Does "Tomahawk for JSF 2.0" works for JSF 2.1 / MyFaces Core 2.1 ?
If not, a new release "Tomahawk for JSF 2.1" is expected/announced anytime soon ?
If not, will there be any downside using "Tomahawk for JSF 2.0" and JSF 2.0 / MyFaces Core 2.0
I am upgrading from MyFaces 1.2.6 + Facelets 1.1.15-jsf1.2 (using lots of templates)
Thanks very much in advance.
Regards,
Kumar.
Yes, Tomahawk for JSF 2.0 will work just fine for JSF 2.1. We also use it in production.
JSF 2.1 is not a specification change, but merely a maintenance release. JSF 1.2 -> 2.0 was however a major specification change and that's why JSF 1.x targeted component libraries won't work for JSF 2.x.
Related
When I go to http://myfaces.apache.org/core22, I see MyFaces JSF 2.2 implementation.
But I'm not seeing Tomahawk for JSF 2.2 in http://myfaces.apache.org/tomahawk. Can I use Tomahawk for JSF 2.0 in JSF 2.2?
There are no API/spec-related (and therefore per definition also no technical) limitations for using a JSF 2.0 compatible component library in JSF 2.2.
Those limitations only exist(ed) when you want to use a JSF 1.x compatible component library in JSF 2.x, primarily because of the replacement of JSP by Facelets as default view technology (JSP tags doesn't work in Facelets).
So, you should be able to just use "Tomahawk for JSF 2.0" or any other JSF 2.0 compatible component library in JSF 2.2 (and 2.1 and 2.3).
I have used JSF 1.x with Tomahawk 1.1.9 in my project and I'm now migrating this project to Websphere 8. I have changed the Faces config and web.xml configuration.
All components are working fine except of t:savestate. I am still using Tomahawk 1.1.9.
Is there any issue in using Tomahawk 1.1.9 version in JSF 2.x application?
You need to upgrade Tomahawk to a JSF 2.x compatible one.
In their download page, pick the one saying "for JSF 2.0" and not the one saying "for JSF 1.2".
We have a old web application which is using JSF 1.1.
We now need to upgrade the JSF version from 1.1 to JSF 1.2. How much effort is required for this?
What are the changes needs to be done in the application?
Is it possible to use Primfaces 3.1 with JSF version 1.2?
If not which is the compatible Primfaces version for JSF 1.2.
Regards
According to this discussion they decided to drop support for JSF 1.2 since version of Primefaces 2
I am using jboss 4.0 and Java 1.5. I want to use JSF, but I know that this version is fit to JSF 1.1 version. Is it possible to use the latest JSF version on JBoss 4.0?
As JSF API is built on top of JSP/Servlet API, the maximum supported JSF version depends on the maximum supported JSP/Servlet version.
JSF 1.0 and 1.1 requires a minimum of Servlet 2.4 / JSP 2.0.
JSF 1.2 works on Servlet 2.4, but requires a minimum of JSP/EL 2.1 which goes hand in hand with Servlet 2.5, so it requires after all Servlet 2.5. If you replace JSP 2.1 by Facelets 1.x as default view technology, then you can use JSF 1.2 on Servlet 2.4.
JSF 2.0 which uses by default Facelets 2.x requires a minimum of EL 2.1 which goes hand in hand with Servlet 2.5, so it requires after all Servlet 2.5. If you supply your own EL 2.1 API/impl, then you can in theory run JSF 2.0 on Servlet 2.4.
JSF 2.1 requires a minimum of Servlet 3.0 and Java 1.6 (6.0).
JBoss 4.x is a Servlet 2.4 container. So if you stick to JSP, then you can at highest use JSF 1.1. But if you replace JSP by Facelets 1.x, then you can use JSF 1.2. JSF 1.2 offers as the most important advantages the possibility to get rid of <f:verbatim>, to use <f:setPropertyActionListener>, to use #PostConstruct, etc.
JSF 2.0 is in theory possible, but I don't guarantee that it will work 100% as I am not fully aware of any possible side effects. I have as far only run it successfully with a very basic test page with an ajax form and a view scoped bean on Tomcat 5.5. It might fail when it goes into the complex. See also Running JSF 2.0 on Servlet 2.4 container.