Don Brown-2 wrote: > >> 2) Should we be implementing each JSF Phase as it's own Struts >> Interceptor >> or should we be using the JSF Lifecycle methods instead? See JSF 1.1 >> Spec - >> Section 11.1. >> > Actually, we are, or at least as much as we can. The JSF lifecycle > methods, found in the Lifecycle class are private and therefore not able > to be called directly. Only execute() and render() are exposed, which > is too high of level to allow for proper integration. Therefore, I > copied the contents of the phase methods (MyFaces HEAD) into new > Interceptors. I'd love to use the Lifecycle class directly, if were > possible. >
I guess I don't understand why the execute() and render() are too high level? What is being done in the Struts implementation of the phases that differs from the default implementation? Why is it not possible to call Lifecycle.execute() to process the first 4 phases. Then let the struts action processing occur. Then in FacesResult use the result uri to create a new UIViewRoot (See MyFaces NavigationHandlerImpl.handleNavigation()). Then call the Lifecycle.rendor(). I don't doubt that there is a reason this doesn't work, I'd just like to understand the flaw in my thinking. --Chris -- View this message in context: http://www.nabble.com/Struts2-JSF-Integration-Proposal-tf2051594.html#a5687383 Sent from the Struts - Dev forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
