I wanted to just bullet point some things so that we can discuss them seperately.
1) One lifecycle vs. two? - Does seperate lifecycles help reduce the possibility of config errors that lead to an action method being called twice? Is there a better way to address this problem than creating seperate lifecycles? 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. 3) Should we add the capability to configure the JSF application, phase listeners, etc. from within the Struts config? How far do we go with this? I'm not sure that we would want to allow navigation, validation, and the like to be configured using the Struts config? 4) Should support be added to allow a uri to be used as part of the Struts result? - I believe this can be done by adding code to the FacesResult to create a new UIViewRoot from the specified uri. I think that is all I have for now. :) Thanks, --Chris -- View this message in context: http://www.nabble.com/Struts2-JSF-Integration-Proposal-tf2051594.html#a5684935 Sent from the Struts - Dev forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
