On Tue, Apr 9, 2013 at 5:36 AM, Antoine Reilles <[email protected]>wrote:
> > Tested on the last 1.6.0 snapshot, it works fine. Thanks a lot ! > I will have code that will be unportable to other stacks, but at least I > will be able make it work. > > +1 Like! As I made big changes in the past... when i migrated from Mojarra 2.1.7 to MyFaces 2.1.8 (because of performance, of course), there was plenty of (unportable) code that worked in Mojarra that clearly did 'not' work in/with MyFaces. Wow, that took my 1 week (7 days) to complete, IIRC, but so glad I made the transition, and honestly, I have no reason to go back to Mojarra! And then when I migrated from JSF managed beans to CDI managed beans; wow, another multiple-day-and-week(s) task that I wanted to complete. Wow, the CDI code that worked in TomEE/OpenWebBeans, surely would 'not' run in Glassfish3.1.2.2/WELD. Does that say/prove that my code was not portable to the RI (reference implementation)? I surely would not say that. My finger will be pointing at Glassfish/WELD, but I've heard that some/many have had success deploying and running CDI managed beans on Glassfish/WELD, but one of those people heard me 'yelling' TomEE everywhere (in the PrimeFaces forums), and this person told me that his CDI app seemed to run a bit faster in TomEE. Go TomEE and OpenWebBeans (reminds me of the blog that Mark Struberg wrote, why is open web beans soooo fast???). :) Since I'm still somewhat junior java/jsf developer, I'll take the blame, my newly-migrated-to-CDI code should have been able to run in-and-via Glassfish/WELD, but Glassfish is too slow for me, and WELD, blah, I have never been able to get CDI code to run via the RI. So, I am forever grateful to this 'tomee' character. :) Um, don't get me started... I will sing TomEE praises! :) Just like I'm stuck on PrimeFaces and sing it's praises, too! :)
