I second Harald on all these points, and to be honest I haven't had the time to test Pax Web width Pax CDI yet. But I'm full of hope that it'll turn out to be playing along nicely since I had this on my roadmap for Pax Web. As you might see you are in an early stage of those two working together, so please expect a bumpy ride right now :)
regards, Achim 2012/7/19 Harald Wellmann <hwellmann...@googlemail.com>: > Hi Christian, > > I'm not sure I understand what you're trying to do with Pax Web on > GlassFish... GlassFish has its own web container which supports WABs, > so why would you want to run another container (i.e. Pax Web) on top > of it? > > Pax CDI is brand new, and so far I haven't tested it in a web context. > The request and session scopes require some special attention, I'd > expect. > > Regarding required dependencies, it usually helps to look at the > integration tests (in this case of Pax Web or Pax CDI) to find a > consistent set of artifacts. Due to the configurable, modular nature > of most Pax projects, it is not possible to provide an all-in-one > archive or a module shopping list. > > 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 turned out that OpenWebBeans works fine, as long as you set an > appropriate thread context class loader. > > 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. > > Hope that helps, > Harald > > 2012/7/19 Christian Beikov <christian.bei...@gmail.com>: >> Hello there! >> >> I tried to get a sample app working with glassfish and Pax Web 2.0 but >> could't really make it work. >> Are there any full step by step guides for getting it running? >> There is for example no list of jars that are required to get basic >> functionallity in the documentation. >> I tried to set that up by looking into the pom files of the projects, that >> was a hard task :/ >> >> Can you maybe provide at least a list of jars that are required or even >> better, an archive that contains all of the required libs for each container >> to work? >> >> My next question is related to CDI support. Are there any plans for >> releasing a weld plugin? You wrote that you were inspired by weld-osgi, so I >> wondered why you did not support weld yet. >> >> It would be really nice if I could use Pax Web and Cdi, because these two >> projects close the gap between OSGi and Java EE! >> >> -- >> Mit freundlichen Grüßen, >> ________________________________ >> Christian Beikov >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/> _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
