>> I've now started implementing a Weld adapter for Pax CDI, hoping to >> make it work without patching Weld itself, or if that fails, to >> understand the exact reasons why weld-osgi had to patch weld-core and >> why this is inevitable.
The patch is due to how we access the right Container instance. Atm we use sort of a singleton mapper to classloader, which works ok in JEE env, due to JEE containers properly setting TCCL, where this is of course not the case in OSGi land, hence the patch, which stores the needed info. >> weld-osgi requires a patched version of Weld. It does not work with >> any official Weld release. This is why I started Pax CDI with >> OpenWebBeans, to find out whether or not the CDI container itself >> would have to be modified to work in and OSGi environment. It's on my todo list, and it's now finally close to the top. :-) I'll try to do a Weld 1.2.x release asap, with Weld-OSGi being part of this release. The long delay is due to Weld API change, which requires AS integration changes, where we were just too late wrt JEE6 cert and/or EAP6. -Ales _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
