The Control Unit Converter bundle allows control units that implement Control Unit API defined in previous releases of the mBS to be managed through the Control Unit Admin defined in this release of mBS.
Contents:
The JAR file of the Control Unit Converter bundle is cuconverter.jar, and is located in the bundles folder.
|
None.
The Control Unit Converter bundle does not register any services.
When started in the OSGi framework, the Control Unit Converter bundle transforms
control units that implement the old Control Unit API, contained in the org.mbs.services.control
package, into control units that implement the Control Unit Provider,
API contained in the org.mbs.services.cu.spi, package. In other
words, if you have registered in the framework control units that implement
the older Control Unit API, the Control Unit Converter bundle will make them
manageable through the Control Unit Admin service.
State variables and action arguments of the following data types can be represented as AttributeDefinitions in the metadata of the converted control units:
Byte, Integer, Short, Long,
Float, Double, Character, String,
Boolean.Vector of the types listed above.
|
The metadata of a converted control unit might be incomplete. Such a case may occur because not all state variables, and action input/output arguments can be converted to AttributeDefinitions because they are not supported by the Control Unit Converter. As a result, the metadata of a converted control unit will not have those actions and state variables.
However, such actions and state variables remain available for usage. You can pass the same arguments to the control unit's actions as you did before the transformation. State variables can be queried as well, and the received results will be without any difference compared with the ones you have previously received.