This content has been marked as final.
Show 4 replies
-
1. Re: About multi bean managers interactive
codeprince Aug 30, 2013 5:10 AM (in response to 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
-
2. Re: About multi bean managers interactive
mkouba Sep 2, 2013 4:00 AM (in response to codeprince)Hi,
if experimenting with CDI and OSGi then look at PAX CDI: https://github.com/ops4j/org.ops4j.pax.cdi
-
3. Re: About multi bean managers interactive
codeprince Sep 2, 2013 10:17 PM (in response to mkouba)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
-
4. Re: About multi bean managers interactive
jharting Sep 6, 2013 9:24 AM (in response to codeprince)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.