Hi Harald, I would prefer that we adopt an OSGI name convention for that feature and not something specific to Pax.
Regards, Charles On Tue, Sep 4, 2012 at 11:03 AM, Harald Wellmann <hwellmann...@gmail.com>wrote: > Hi Charles, > > thanks a lot, I'll try that with Pax CDI. This will require some > preparation, though... > > The point is that the OSGi CDI RFP requires an opt-in mechanism for > CDI-enabled bundles, and I'm currently using a specific manifest > header > > Pax-ManagedBeans: META-INF/beans.xml > > Bundles without that header will not be picked up by the CDI extender, > even if they contain a beans.xml resource. > > So testing would be trivial if these headers were present, otherwise > I'll have to implement a way to opt out of opt-in ;-). > > Would it be an option for DeltaSpike to include this preliminary > header, until the OSGi Alliance has specified the details of the > opt-in mechanism? > > Best regards, > Harald > > > 2012/9/4 Charles Moulliard <ch0...@gmail.com>: > > Hi Harald, > > > > I have added OSGI support for DeltaSpike Core, Impl and JPA modules and > > deployed them successfully on Karaf. Can you make some tests please ? > > > > https://issues.apache.org/jira/browse/DELTASPIKE-210 > > > -- Charles Moulliard Apache Committer / Sr. Pr. Consultant at FuseSource.com Twitter : @cmoulliard Blog : http://cmoulliard.blogspot.com