Hi,
Your observation is correct. You either get the packages which the
framework determined is available from the VM or you have to provide the
complete list in the org.osgi.framework.system.packages yourself. In OSGi
R4.2 (implemented in Equinox 3.5) we have added added a new property
Looking at the Equinox implementation of the Metatype service (the version
at the head of the trunk in CVS), it appears that the validate() method in
AttributionDefinitionImpl only performs validation on strings. Could
someone confirm if this is indeed the case, and if so, whether there are any
Hi Jan,
There are currently no plans for further work in 3.5 however if you open a
bug and submit a patch I'd definitely look at it.
-Simon
|
| From: |
|
Hi Simon, thanks for your quick reply. I've actually realised that it also
validates ranges of numerical attributes if min and max are set. I'll see if
the existing validation meets all our needs, and raise a bug report if not.
Regards,
Jan
2009/4/8 Simon Kaegi simon_ka...@ca.ibm.com
Hi Jan,
Can anyone provide me better details to the current state of the
transport layer for P2? We need to support provisioning, but our only
available transport layer will be JMS. If the P2 transport layer is
based on ECF, I was hoping it might be possible to simply plugin a JMS
transport and ride on
This was one of the goal of using ECF. I'm happy to see someone realizing
this :-)
We have not tried this ourselves, but we have been changing the
implementation of the http transport without changing the p2 code so this
should work (maybe some work needs to be done in ECF around error codes).
Hi All,
Yes this is one use case that ECF was introduced to support.
Incidently, we do already have JMS-based providers for ECF...although
there is a small amount of remaining work to support the filetransfer API.
See/join the ecf-dev mailing list here:
