|
|
 |
 |
 |
 |  |
 |
 |
Forums >>
JVMS
Chuck, there's some confusion over the Device Manager
component. It's listed in the tools we want to have
available in the Platform Component view; but as far as we
can tell, there's no 'Device Manager' type specified in the
SCA. So the question is this: what does it mean for a
component to be a Device Manager, and what kind of support
is required in JVMS?
Thanks!
-Garrett
|
The intention is that a devicemanger can be included, as it
typically has a uses port to be connected to a logger. This
is a recent SCA 2.2 change, so I expect things are a bit
half baked.
The componenttype field on D-30 includes devicemanager. The
componentrepid (top level) according to the SCA must be one
of 3 things, of which this is not. Let's assume for the
moment that a DeviceManger would get a value here of
"IDL:CF/DeviceManager:2.2" - this seems to make sense. Note
that in this case (even though it seems a bit stupid), this
same interface would need to show up in the interfaces
section, and would be cited in either the supportsinterface
or as a port, depending on how the developer was feeling
that morning...
Hope this helps,
Chuck
|
The intention is that a devicemanger can be included, as it
typically has a uses port to be connected to a logger. This
is a recent SCA 2.2 change, so I expect things are a bit
half baked.
The componenttype field on D-30 includes devicemanager. The
componentrepid (top level) according to the SCA must be one
of 3 things, of which this is not. Let's assume for the
moment that a DeviceManger would get a value here of
"IDL:CF/DeviceManager:2.2" - this seems to make sense. Note
that in this case (even though it seems a bit stupid), this
same interface would need to show up in the interfaces
section, and would be cited in either the supportsinterface
or as a port, depending on how the developer was feeling
that morning...
Hope this helps,
Chuck
|
|  |
|