-
Notifications
You must be signed in to change notification settings - Fork 38.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full support for JSF 2.0 [SPR-5585] #10256
Comments
Ward Maenhout commented JSR-314 went final on 01 Jul, 2009. |
Juergen Hoeller commented Yes, this has even been done for Spring 3.0 already. Marking this as fixed in 3.0 then. Juergen |
Ward Maenhout commented Are you sure this is done? tested with the 3.0.0.RC1 |
Juergen Hoeller commented Note that DelegatingVariableResolver is only really meant for use with JSF 1.1. As of Spring 2.5, SpringBeanFacesELResolver is available for use with JSF 1.2 or higher: This should work fine with JSF 2.0 as well as far as we tested. Let me know if you encounter further problems with JSF 2.0. We can still revise our JSF support for 3.0 RC2/GA where necessary. Juergen |
Ward Maenhout commented Ok, seems I was reading the wrong documentation. The application runs, but in my page my original bean is not resolved. Is see my #{} showing up in my page. I would like to get this working as a plan to write a tutorial afterwards and even extend it to build a JSF 2.0/SPRING 3.0 portlet later. |
Ward Maenhout commented Extra, nothing that is jsf 2.0 related is renderen in my page. (h:commandbutton is not renderend, but also not shown in the jsp or source of the page that is rendered) |
Ward Maenhout commented I succesfully integrated spring 3.0.0.RC1 with JSF 2.0. <listener> |
Juergen Hoeller opened SPR-5585 and commented
We will be providing compatibility with Mojarra 2.0 beta releases - and hence the JSF 2.0 public review API there - in Spring 3.0 RC1 already.
However, full support for JSF 2.0 will have to wait for the JSR-314 spec going final, which is currently scheduled for September. Spring 3.1 will be catching up with it.
1 votes, 5 watchers
The text was updated successfully, but these errors were encountered: