-
1. Re: Migration from JSF1.2 to JSF2
pomcompot Sep 6, 2010 11:52 AM (in response to pomcompot)Another point, will <rich:componentControl /> still be supported with JSF2 AJAX support ?
-
2. Re: Migration from JSF1.2 to JSF2
ilya_shaikovsky Sep 8, 2010 3:19 AM (in response to pomcompot)Will it need some adaptations of existing code ? We are already using Facelet mechanism. Is there some points of RichFaces 3.x that must not be used in order to provide a better migration to JSF 2 ?
Facelets is a standard VDL of JSF 2 so there should not be general problems. As for RichFaces - we broke backward compatibility in order to make revising during major version change. So some updates like attributes names or even components names - potentially could be needed.
Concerning the AJAX support offered by RichFaces, JSF 2 has a support of AJAX. Does it change anything if we are using AJAX components of RichFaces ?
http://mkblog.exadel.com/2010/08/what-richfaces-a4jajax-adds-on-top-jsf-2-fajax-tag/ and some more in our documentation(currently draft so some info could be in progress ).
Does the RichFaces resource framework mechanism (resource:///) will be preserved ?
we will use standard JSF 2 resources mechanism.
What are the best practices to minimize migration cost ?
From our side - we could only provide you good migration guide, and it's already available in draft. http://docs.jboss.org/richfaces/latest_4_0_X/Migration_Guide/en-US/html/
Another point, will <rich:componentControl /> still be supported with JSF2 AJAX support ?
It's already available in 4.x milestones as a behavior.
-
3. Re: Migration from JSF1.2 to JSF2
pomcompot Sep 15, 2010 9:57 AM (in response to ilya_shaikovsky)Thanks a lot for your answers.
About the resource mechanism, you say:
we will use standard JSF 2 resources mechanism.
Does it means that both resource:/// and #resource will be supported and that resource:/// will behind use the standard JSF2 mechanism, or that resource:/// will be no more usable?