Skip to content
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

Closed
spring-projects-issues opened this issue Mar 19, 2009 · 7 comments
Closed

Full support for JSF 2.0 [SPR-5585] #10256

spring-projects-issues opened this issue Mar 19, 2009 · 7 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

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

@spring-projects-issues
Copy link
Collaborator Author

Ward Maenhout commented

JSR-314 went final on 01 Jul, 2009.
Is it possible that full support for JSF 2.0 comes in the final spring 3.0.0 release?

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Yes, this has even been done for Spring 3.0 already. Marking this as fixed in 3.0 then.

Juergen

@spring-projects-issues
Copy link
Collaborator Author

Ward Maenhout commented

Are you sure this is done?
I tried using the DelegatingVariableResolver to resolve my managedproperties, but it does not work.
Also the source code still states JSF 1.2 and nothing on 2.0

tested with the 3.0.0.RC1

@spring-projects-issues
Copy link
Collaborator Author

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

@spring-projects-issues
Copy link
Collaborator Author

Ward Maenhout commented

Ok, seems I was reading the wrong documentation.
I tried it now with The SpringBeanFacesElResolver, added spring-web and spring-beans to my pom.xml and added the needed stuff in the facesconfig.
Note that this is the only thing I have in the facesconfig as I use the annotations.
I had a jsf 2.0 application working with 1 bean, and now I try to add inject an other bean into this one using spring.

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.

@spring-projects-issues
Copy link
Collaborator Author

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)

@spring-projects-issues
Copy link
Collaborator Author

Ward Maenhout commented

I succesfully integrated spring 3.0.0.RC1 with JSF 2.0.
Toke me some thing to figure out that I still need the context listener in my web.xml

<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 RC1 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants