I think it should also work in 1.7.1. This is actually not a bug but basically some modularity feature you get from OpenWebBeans. Basically CDI is JavaEE6. But in OpenWebBeans we still support a lot of older integration scenarios as well. And even pure Java SE. OWB is built around a ‚core‘ which has only 450k and supports SE + interceptors, decorators, etc (in comparision to our size even Guice with it’s 3.5MB looks fat). All other EE integration features are added as ‚OpenWebBeans-plugins‘.
As TomEE-1.7.x targets EE6 and TomEE-2.0.x even EE7 it by default packages the JSF2 support module. The difference between JSF-1.2 and JSF-2 is mainly the handling of the ‚Application‘ interface [1]. Up to JSF-1.2 you had to implement a custom Application (we need that to attach our own CDI EL-Resolver) for each JSF version. And the Application interface got changed a lot with each JSF version. To not having to provide an own version of JSF integration code over and over again the JSF EG decided to introduce an Abstract ApplicationWrapper base class [1]. This is what we use by default in our webbeans-jsf (that is JSF2) module. The webbeans-jsf12 module cannot use this new abstract class though. And that is the reason why you need to switch those 2 jars if you like to run with a JSF-1.2 container like Mojarra-1.2. LieGrue, strub PS: I always prefer explaining those kind of things to developers instead of simply telling them what to do in a blackbox kind of way. We are all cooking with water still - although our water is pretty damn hot sometimes ;) [1] http://docs.oracle.com/javaee/6/api/javax/faces/application/Application.html [2] http://docs.oracle.com/javaee/6/api/javax/faces/application/ApplicationWrapper.html > Am 10.04.2015 um 16:25 schrieb Romain Manni-Bucau <[email protected]>: > > 2015-04-10 16:09 GMT+02:00 kvrohit <[email protected]>: > >> Hi Romain, >> >> Thanks for the quick response! I see that a defect has been opened for >> this. >> I took a look at it and it says Fixed in 2.0.0-Milestone-1. So, have a few >> follow up questions: >> >> 1. Can I use 2.0.0 to deploy my app? If so, where can I download it? >> > > Not yet, few other things are blocking - not sure anymore it is 2.x > specific or in 1.7 as well > > >> 2. What is the general availability for 2.0.0? >> > > Soon hopefully - 1st quarter > > >> 3. Will this fix be back ported to 1.7.1? >> > > Can be > > Note: you still need to replace openwebbeans-jsf by openwebbeans-jsf12 in > tomee/lib cause of changes in JSF API > > >> >> - Rohit >> >> >> >> -- >> View this message in context: >> http://tomee-openejb.979440.n4.nabble.com/Does-TomEE-1-7-1-support-JSF-1-1-tp4674353p4674363.html >> Sent from the TomEE Users mailing list archive at Nabble.com. >>
