Hi Guillaume,
sorry for my late feedback.
My comments inline:
* when deploying a spec bundle, we need to hide the packages from the jre
and by doing so we forbid the use of the implementation provided by the jre
Good idea. As we discussed last week, this could be handle by the Karaf
profiles (using patch/diff/merge mechanism). We can also enhance the
karaf-maven-plugin to provision the spec bundle in the lib/endorsed.
At least, we have always the "custom distribution" way using an assembly.
* when deploying an implementation, it won't be available until the
bundle is started but this constraint isn't captured
The first read about the new OBR spec looks interesting for this point.
Having some kind of events, with callback handlers, will allow us to react.
Waiting for the new OBR, maybe we can implement a specific behavior for
spec. We can imagine to add an specific attribute in the MANIFEST
(SpecBundle or something like that), and handle a specific life cycle
and events for this kind of bundles (monitoring the directory for
instance).
Another way is to have a Spec OSGi service specific to handle the Spec
bundle live cycle. We can imagine that the Spec bundle expose a given
service interface with properties describing the services. In that case
we can have a service tracker to know when the service is started and ready.
I'm not sure it's good ideas, but it's the only ones that I have for now ;)
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
