Also, you may want the non-PLUME release of TomEE(+) 1.7.0, and replace myfaces 2.1.15 JARs with myfaces 2.2.4 (api/impl) JARs.
I think TomEE PLUME release may have config + jars to make it work specifically for Mojarra users. Of course, non-PLUME release will not have that config + jars. :) On Thu, Aug 28, 2014 at 5:29 PM, Felipe Jaekel <fkjae...@gmail.com> wrote: > TomEE works fine with MyFaces 2.2, just replace the 2.1 jar with it. > > One observation is that in my case when I changed from Mojarra 2.1 to > MyFaces 2.1 I had to do some adjustments in my applications, and some more > adjustments when I changed from MyFaces 2.1 to 2.2, so I would recommend > you to test your whole application with MyFaces before deploying it in > production. > > > 2014-08-28 17:53 GMT-03:00 cocorossello <cocorosse...@gmail.com>: > > > Hi, > > > > I'm moving from glassfish 4.1 to tomEE 1.7.0. I started with PLUME for an > > easier start, but now I want to use myfaces instead of mojarra (I've seen > > some performance problems that might be my fault, but it improves a lot > > with > > myfaces). > > > > My question is if it's safe to just upgrade myfaces to last version > (2.2.4) > > or if I should stick with 2.1.x > > > > Thank you. > > > > > > > > -- > > View this message in context: > > > http://tomee-openejb.979440.n4.nabble.com/Upgrade-myfaces-version-in-Tomee-1-7-0-tp4671458.html > > Sent from the TomEE Users mailing list archive at Nabble.com. > > >
