2.2 stability
Hello everyone, For those of you who have had a chance to kick the tires with 2.2, how stable is it so far? For the developers, can you give me a sense of how much of the code base was touched for this release? I'm trying to evaluate whether or not it's ready for one of my clients (it will be hard sale, since it's so new). ___ Kito D. Mann | @kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com | @jsfcentral +1 203-998-0403 * Listen to the Enterprise Java Newscast: *http://w http://blogs.jsfcentral.com/JSFNewscast/ww.enterprisejavanews.com http://ww.enterprisejavanews.com* * JSFCentral Interviews Podcast: http://www.jsfcentral.com/resources/jsfcentralpodcasts/ * Sign up for the JSFCentral Newsletter: http://oi.vresp.com/?fid=ac048d0e17
Re: 2.2 stability
Hi, Im sure others know better but here's my story as early adopter. I am -1 against adoption if you use c:forEach because it's been rewritten or greatly improved upon somehow. As a consequence I was blocked by MYFACES-3853 https://issues.apache.org/jira/browse/MYFACES-3853 for a while. As a fix I used the new parameter: context-param param-nameorg.apache.myfaces.STRICT_JSF_2_FACELETS_COMPATIBILITY /param-name param-valuetrue/param-value /context-param And I upgraded to a snaphot fast. That same snapshot messed up the id generation for me if I kept above parameter, luckily everything worked when I removed it but I still got that card house feeling. To summarize I think above parameter is broken in 2.2.1 but I have not tried to reproduce and ofc could be my setup somehow. Also I am contemplating dropping TomEE as my appserver and use mojarra for now because of MYFACES-3865https://issues.apache.org/jira/browse/MYFACES-3865 ... I have a release in two days and at this point I just need everything to work. Again it might just be me (all though MYFACES-3865https://issues.apache.org/jira/browse/MYFACES-3865 has at least two other reporters as seen in the linked conversation on the list). Getting mojarra to work with TomEE failed for me so something has to give and It seems I will fall back on Tomcat, use Mojarra and then reattempt myfaces and TomEE for at a later release. My other smaller app, my side projects, etc. Are all working fine (they also don't need any enctype=multipart/form-data that I have trouble with). cheers On 9 March 2014 20:27, Kito Mann kito.m...@virtua.com wrote: Hello everyone, For those of you who have had a chance to kick the tires with 2.2, how stable is it so far? For the developers, can you give me a sense of how much of the code base was touched for this release? I'm trying to evaluate whether or not it's ready for one of my clients (it will be hard sale, since it's so new). ___ Kito D. Mann | @kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com | @jsfcentral +1 203-998-0403 * Listen to the Enterprise Java Newscast: *http://w http://blogs.jsfcentral.com/JSFNewscast/ww.enterprisejavanews.com http://ww.enterprisejavanews.com* * JSFCentral Interviews Podcast: http://www.jsfcentral.com/resources/jsfcentralpodcasts/ * Sign up for the JSFCentral Newsletter: http://oi.vresp.com/?fid=ac048d0e17
Re: 2.2 stability
I found 2.2 to be very stable, almost a drop in replacement for 2.1. Using the new file upload feature of JSF 2.2 was straightforward for me. I had a hard time with Faces Flows, but Leonardo and the others kindly helped and fixed a few bugs - I still have to test that it is ok. I expected many more problems to come with this new major release. I would advise anyway anyone who does not have some experience with JSF and is not ready to fire his debugger when encountering a strange behaviour to wait for 2.2.1 or 2.2.2 and for DeltaSpike 0.6. There are very few glitches given the bunch of new features, but these are still glitches. To those persons I would advise latest JSF 2.1 + latest CODI for the time being. Best regards, Ludovic On 9 mars 2014 20:27:31 UTC+01:00, Kito Mann kito.m...@virtua.com wrote: Hello everyone, For those of you who have had a chance to kick the tires with 2.2, how stable is it so far? For the developers, can you give me a sense of how much of the code base was touched for this release? I'm trying to evaluate whether or not it's ready for one of my clients (it will be hard sale, since it's so new). ___ Kito D. Mann | @kito99 | Author, JSF in Action Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting http://www.JSFCentral.com | @jsfcentral +1 203-998-0403 * Listen to the Enterprise Java Newscast: *http://w http://blogs.jsfcentral.com/JSFNewscast/ww.enterprisejavanews.com http://ww.enterprisejavanews.com* * JSFCentral Interviews Podcast: http://www.jsfcentral.com/resources/jsfcentralpodcasts/ * Sign up for the JSFCentral Newsletter: http://oi.vresp.com/?fid=ac048d0e17 -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté. | | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. |
Re: 2.2 stability
On Sun, Mar 9, 2014 at 5:20 PM, Ludovic Pénet l.pe...@senat.fr wrote: I found 2.2 to be very stable, almost a drop in replacement for 2.1. +1 I was using MyFaces 2.1.13 prior using MyFaces 2.2.0 (final), and MyFaces 2.2.0 seems just as stable as 2.1.13 is/was. I'm very pleased/satisfied with myFaces 2.2.0, and i have had 'no' issues at all. :)
Re: 2.2 stability
Hi @MYFACES-3865 It was fixed in 2.2.1, and the artifacts will be released in no time. The fix for c:forEach was really complex and painful, but it was finally done and the result is the best option we will have. Finally we have a proper solution that will work in complex cases and will allow all facelets dinamic tags to work well together. The hack done for: org.apache.myfaces.STRICT_JSF_2_FACELETS_COMPATIBILITY Is meant for people that requires the old (and buggy) logic from facelets 1.1.x, so it is expected to do not work in some cases. My personal perception is 2.2.1 will be very stable, it is obvious to have some small bugs, but in this release we created a lot of junit tests, so the probability of find bugs has become small. Anyway, we will be eager to check and fix all new issues as soon as possible. regards, Leonardo Uribe 2014-03-09 18:26 GMT-05:00 Howard W. Smith, Jr. smithh032...@gmail.com: On Sun, Mar 9, 2014 at 5:20 PM, Ludovic Pénet l.pe...@senat.fr wrote: I found 2.2 to be very stable, almost a drop in replacement for 2.1. +1 I was using MyFaces 2.1.13 prior using MyFaces 2.2.0 (final), and MyFaces 2.2.0 seems just as stable as 2.1.13 is/was. I'm very pleased/satisfied with myFaces 2.2.0, and i have had 'no' issues at all. :)
[ANNOUNCE] MyFaces Core v2.0.21 Release
The Apache MyFaces team is pleased to announce the release of MyFaces Core 2.0.21. MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by JSR-314. MyFaces Core has passed Sun's JSR-314 TCK and is 100% compliant with the JSR-314 specification. MyFaces Core 2.0.21 is available in both binary and source distributions. * http://myfaces.apache.org/download.html MyFaces Core is also available in the central Maven repository under Group ID org.apache.myfaces.core. Release Notes - MyFaces Core - Version 2.0.21 Bug [MYFACES-3847] - HtmlStylesheetRenderer doesn't ignore additional link parameters when checking for the resource [MYFACES-3857] - Unbalanced pushComponentToEL/popComponentFromEL in processUpdates regards, Leonardo Uribe
[ANNOUNCE] MyFaces Core v2.1.15 Release
The Apache MyFaces team is pleased to announce the release of MyFaces Core 2.1.15. MyFaces Core is a JavaServer(tm) Faces 2.1 implementation as specified by JSR-314. MyFaces Core has passed Sun's JSR-314 TCK and is 100% compliant with the JSR-314 specification. MyFaces Core 2.1.15 is available in both binary and source distributions. * http://myfaces.apache.org/download.html MyFaces Core is also available in the central Maven repository under Group ID org.apache.myfaces.core. Release Notes - MyFaces Core - Version 2.1.15 Bug [MYFACES-3847] - HtmlStylesheetRenderer doesn't ignore additional link parameters when checking for the resource [MYFACES-3850] - html EL expression inside markup enables escape on static text in facelets jspx mode [MYFACES-3854] - oam-compress-spaces remove carriage return / line feed in CDATA sections [MYFACES-3857] - Unbalanced pushComponentToEL/popComponentFromEL in processUpdates regards, Leonardo Uribe
[ANNOUNCE] MyFaces Core v2.2.1 Release
The Apache MyFaces team is pleased to announce the release of MyFaces Core 2.2.1. MyFaces Core is a JavaServer(tm) Faces 2.2 implementation as specified by JSR-344. The artifacts passed the TCK test of Feb 2013 (jsftck-2.2_26-Feb-2013.zip). MyFaces Core 2.2.1 is available in both binary and source distributions. * http://myfaces.apache.org/download.html MyFaces Core is also available in the central Maven repository under Group ID org.apache.myfaces.core. Release Notes - MyFaces Core - Version 2.2.1 Bug [MYFACES-3845] - Invalid modification of facesConfig.getFacesFlowDefinitions() collection when implicit flow definition is derived [MYFACES-3847] - HtmlStylesheetRenderer doesn't ignore additional link parameters when checking for the resource [MYFACES-3850] - html EL expression inside markup enables escape on static text in facelets jspx mode [MYFACES-3853] - ui:include not working inside c:forEach [MYFACES-3854] - oam-compress-spaces remove carriage return / line feed in CDATA sections [MYFACES-3857] - Unbalanced pushComponentToEL/popComponentFromEL in processUpdates [MYFACES-3858] - Faces Flow startNode is not defined by default for xml non empty files ending with -flow.xml [MYFACES-3859] - Allow use the flowId as a nodeId inside the same flow [MYFACES-3860] - UIViewRoot.restoreViewScopeState(...) is not being called from DefaultFaceletsStateManagementStrategy [MYFACES-3861] - impl-test module using unpack plugin does not allow generate site Improvement [MYFACES-3846] - Implement temporal resourcehandler cache for JSF 2.2 contracts [MYFACES-3862] - Set mock InitialContextFactory for junit testing with myfaces impl test regards, Leonardo Uribe
