I have to admit that I'm not completely up to speed yet with all the new functionality in Struts2. I will have to look at the wild card stuff to get a better idea of what it can do. In the mean time maybe you can give me a short rundown of how you see the wild cards working with the JSF integration?
As for the two lifecycles vs one discussion, my biggest concern is that we be able to determine as easily as possible whether or not we should allow Struts to execute a call to the action class. For instance. Assume that the JSF application has been configured with a backing bean and that backing bean is also being used as a Struts Action class. I could see this happening in a scenario where someone started as a pure JSF application, then integrated into Struts, and then wanted to add a new function to the existing backing bean but wanted to use Struts to manage the processing rather than using the JSF event processing. Bottom line is I think it could happen that both JSF and Struts could be configured that they both think that they are to make the call to the same action method. This would lead to the method being called twice, once by JSF and once by Struts. This would at a minumum cause performace issues and at worst cause issues with state management. This is really a configuration issue but I think it would be easy to do by accident and hard to detect once you had it configured incorrectly because at first glance the application would probably still work. After thinking about this over the weekend I'm not sure that even the proposel for seperate lifecycles completely prevents this. It will only correct the issue for the scenario where you are using JSF to handle action calls and are by passing the Struts Action call. I can't see a way to prevent JSF from calling the action if it is configured to do so. That would mean that if you were using Struts do do the action method invocation that you could still not garuantee that JSF was not also invocing the action method. The ideal solution would be to call JSF and then have JSF tell us if it invoked the action or not. If JSF did the work we would know to by pass the call to the Struts Action. Unfortunetly I have not been able to find anything in the JSF 1.1 Spec that could be used to know this. So with all of that being said, is my issue still as clear as mud? :) Maybe I should create a small example using the showcase employee app to verify that this really is a potential problem? Sometimes code is clearer than email! Thanks, --Chris -- View this message in context: http://www.nabble.com/Struts2-JSF-Integration-Proposal-tf2051594.html#a5684125 Sent from the Struts - Dev forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
