[ https://issues.jboss.org/browse/RFPL-2506?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on RFPL-2506: ------------------------------------- By the time I was investigating this, Oracle website was under maintenance so following information was taken from the second [link|http://jdevelopment.nl/jsf-22/] only (will check the first one asap). There are many feature but as described in this issue there are several "bigger" which we should focus on. This is a first scratch of what I have found to give you some feedback on this issue, I will report more details as soon as I read more information on this topic. Feel free to edit this post in case I got anything wrong. * *[File Upload component|http://jdevelopment.nl/jsf-22/#802]* ** I believe this was partially mentioned [here|https://issues.jboss.org/browse/RF-13444] ** The new component still does not support the file upload progress (however neither does our implementation atm - see discussion above) ** Testability: Maybe test cooperation of JSF fileUpload and RF fileUpload when both are present on the same page? Otherwise no tests are needed I think (since we use our implementation which we test already) * *[CSRF|http://jdevelopment.nl/jsf-22/#869] (cross site request forgery)* ** This is an increasement in matters of security, I found a nice guide [here|http://apex.oracle.com/pls/apex/f?p=44785:24:100843396589482::NO::P2...] showing how to implement it ** Testability: I cannot really imagine how to test this (since we could only see there is a token when page is accessed via non-postback) and if it would do any good to test this. * *[HTML5 markup|http://jdevelopment.nl/jsf-22/#1089]* ** The main thing here is _pass-through_ attributes, adding a support for _type_ attributes in _input elements_ ** Testability: I suppose we could test this quite easily. Just taking all the _input components_ and adding the passThrough tag would do the trick since it should affect the HTML markup which we can test. * *[FacesFlows|http://jdevelopment.nl/jsf-22/#730]* ** Introduces a new annotation {{@FlowScoped}}, this is generally useful for usage like wizard creation when we know where does the flow start and ends precisely. ** Testability: I suggest we add a new test (a somewhat modification of current showcase r:togglePanel - Wizard creation, or any other similar) where we use this new annotation and test components behave corectly. * *[Multi Templating|http://jdevelopment.nl/jsf-22/#1142]* ** This feature should have been much bigger in original JSF reports but it was (due to time shortage) limited only to "small addition" ** Allows to use multiple templates placed in extra directory ** Testability: We should test this feature in combination with RF (where we turn off skinning) to see how it cooperates and whether it affects RF components and how. * *Loading Facelets via ResourceHandler* ** I am currently searching for some more information as I am struggling to figure out how does this work (and how you achieved the same before) * *Other features* ** Yet to be investigated Other information concerning QE status on JSF 2.2: * As for automated tests, there is a Jenkins job running Metamer tests on WildFly - [link|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/richfaces-5.0-me...] * I am also verifying issues from [epic link|https://issues.jboss.org/browse/RF-13080] - most are resolved and closed already. * [~jstefek] is investigating stateless setup so I suppose he will post his results here as well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira