About multi bean managers interactive

[codeprince]

Hi,

I have a question as following:

I am implementing some dynamic Java EE feature combined with OSGi,

I have a wab(web bundle) called "wab1" using JSF 2 and CDI, and while deploying the wab, a bean manager called bm1 is created.

Then, I plan to deploy another wab called "wab2" which also uses JSF 2 and CDI, and among wab2, there is a CDI Bean as following,

@Named

@RequestScoped

public class AboutBean {

    private String message;

    /**

     * @return the message

     */

    public String getMessage() {

        return message;

    }

...

While deploying wab2, I wish AboutBean can be also registered into bm1 from wab1. Common way should be impossible(Maybe I am wrong). So,

I design a CDI extension and add some annotation into AboutBean to notify CDI extension.

@Named

@RequestScoped

@DynamicBean(ContextPath="wabsample")    ---> My imaginary way

public class AboutBean {

    private String message;

    /**

     * @return the message

     */

    public String getMessage() {

        return message;

    }

...

ContextPath="wabsample" is wab1's context path in order that CDI extension can find bm1 by the property.

So, here's critical point is that CDI extension can find bm1 by some way, my question is that is there any way to find bm1?

Any other idea is good, thanks!

Tang

[codeprince]

Maybe a solution is to register bm1 as OSGi Service, then CDI Extension Module can obtain the bm1 by OSGi registry.

However, whether having other good ideas?

Thanks

Tang

[mkouba]

Hi,

if experimenting with CDI and OSGi then look at PAX CDI: https://github.com/ops4j/org.ops4j.pax.cdi

[codeprince]

Thanks Martin's reply.

The feature I will implement has a litter different from normal OSGi/CDI, and the feature is not described in RFC 193.

Best Regards

Tang

[jharting]

This won't work. Weld has certain assumptions about the deployment. One of them is that the deployment is static and does not change after bootstrap. The other approach implemented by weld-osgi and pax cdi where multiple CDI containers with static deployment are integrated is much more fitting.