Matt Raible wrote:
<quote>
Your best bet is to use Spring's DelegateVariableResolver.
http://www.springframework.org/docs/api/org/springframework/web/jsf/ DelegatingVariableResolver.html
This works with MyFaces just fine (I'm using 1.0.7), but MyFaces does spit out warnings about properties that can't be resolved (even though they're correctly resolved by the DelegateVariableResolver).
Matt
</quote>
Hi Matt:
Up to now, i manually connect Jsf component with Spring components. Would you explain what happens in the following case:
1) A jsf session managed bean (portalTabbedBean) is called the first time a user hits the site. The portalTabbedBean is connected to a non-singleton Spring bean (portalProcessor) which provides hooks to singleton facilities managed by Spring.
2) Currently i connect these 2 by looking at the user session to see if it has an instance of portalProcessor. If not, i instantiate the portalProcessor, connect to the portalTabbedBean and put it in as a session attribute. The lifecycles of both beans go with the user session.
3) Now, if i use Spring Jsf support to connect Jsf portalTabbedBean with Spring portalProcessor, what is the lifecycle of non-singleton portalProcessor? and how do i programmatically access the instance of Spring portalProcessor since there is now NO user session attribute attached to the bean (portalProcessor)?
Thanks
BaTien DBGROUPS
