If the solution is not implemented by extending view..
If the solution is not implemented by extending view will the spring features of implementing the view in whatever technology you want be still true? I'm looking forward to hear Craig's implentation ideas...
Wouldn't an irc channel be more efficient than dev list?
Wouldn't an irc channel be more efficient than dev list? In a way that discussions could be archived on the site for community review?
Well these are my thoughts...
I thought the extended view idea was the best way because it fit into the current architecture. I never liked the idea of the Faces servlet because it doesn't give any leverage to decide what to do based on the request. Using the spring controler to proxy to jsf view gives spring full control of what to do as a result of the request either proxying to faces stuff or any other technology. In the meantime spring interceptors can be applied. This is particularly important with portlet development since filters are not yet supported.
*How would you allow to use JSF flows?
The view resolvers handle this not the flow as far as I understand.
*How can both flow models be integrated in one web application?
According to doc "When mixing different view technologies in a web application, you can use the ResourceBundleViewResolver" the alternative method is "Spring supports more than just one view resolver"
My thought was if the view is a faces implementation it must have access to facesContext somehow. If the post is back to the same view with the component then I don't see why all those features wouldn't be supported.
*Does it support the use of JSF features (i.e. bindings, validators, converters)?
Nothing would have changed wrt architecture so I also don't see why that would change.
*Can you still use available JSF/web flow design tools?
I wouldn't consider me the expert here. I'm glad we've got some real experts involved. I'm not proposing any solution, I just realized I had a need and tried to get some idea what was involved. I think between Keith and Craig a far superior solution will be developed than I could have done. I just hope my business need to support JSF in portlets with this architecture will be realized.
*Beside the integration of different view technologies, do you see any important advantages that favor your approach over the other?