For more information about this bug, visit
A new bug was added:
Summary: motion control components do not have 'standard'
constructor (for dynamic loading)
Product: OCL
Version: trunk
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: P2
Component: Motion Control
AssignedTo: orocos-dev [..] ...
ReportedBy: peter [dot] soetens [..] ...

All nAxes components take an extra argument, besides the name, denoting the
number of axes. This non standard constructor prevents these components to be
dynamically loaded by the DeploymentComponent.
All Cartesian components take an extra argument, besides the name, denoting a
property filename. This non standard constructor prevents these components to
be dynamically loaded by the DeploymentComponent.

This can be dirty-fixed by creating a new constructor or setting a 'default'
value to the number of axes or property filename. The clean-fix is to make the
number of axes and property filename a property and implement configureHook()
which checks this value and resizes the work vectors and/or reads the property
file.