>>>>> Marc Schlegel <[email protected]>: > Hi Steinar. > The problem is, that JSF doesn`t provide any means to handle OSGi services. > CDI would solve this but at the moment it is not possible to use > CDI-Annotations in a JSF-Controller (UkelonnController) because JSF inside > Pax-Web cannot resolve beans within an BeanManager from an EL-Expression > [1]. If this bug would be solved you could just use the CDI-Extensions > provided by Pax-CDI.
Hm... I have to read up on BeanManagers...? Is there a Pax Web OSGi service, that will let me get hold of the JSF servlet's BeanManager? FWIW I already have the relevant OSGi service captured in a BundleActivator in the bundle. My own home-written activator http://sbang.github.io/jsr330activator/ The problem is how to make give the beans a reference to the services, or the activator object, without resorting to a singleton with static accessor...? Thanks! - Steinar -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
