2012/7/19 Ales Justin <ales.jus...@gmail.com>: > 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. >
Ales, thanks for clarifying. Yes, I've now run into the issue with the Container singleton, which is handled differently in OpenWebBeans. >From the osgi branches of your Weld Github forks alesj/api and alesj/core, I locally built a weld-osgi-bundle 1.2.0-SNAPSHOT which plays nicely with Pax CDI, using a new pax-cdi-weld adapter. So once Weld 1.2.x is out, Pax CDI will be able to provide equivalent functionality for both of Weld and OpenWebBeans. The trouble is, while this works for me locally, we can't release Pax artifacts based on third-party snapshots, and our CI jobs will also break as soon as I commit the new pax-cdi-weld module. I'll try to mask Weld support with a Maven profile and/or push Weld 1.2.0 snapshots to our OPS4J snapshot repository so that people can provide feedback on this approach without having to build the whole lot and all dependencies for themselves. Best regards, Harald _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
