e for the integrated lifecycle part,
thanks in part to Rod Browns efforts. Let me know if I should continue to
work on this.
Thank You,
--Chris Waring
--
View this message in context:
http://www.nabble.com/Struts2-JSF-Integration-Proposal-tf2051594.html#a5651702
Sent from the Struts - Dev
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
integrat
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 sepe
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
Don Brown-2 wrote:
>
>> 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
Is the XWork 2.0 source available anywhere? I can't seem to locate it.
--
View this message in context:
http://www.nabble.com/Where-is-the-XWork-2.0-Source--tf2114907.html#a5831160
Sent from the Struts - Dev forum at Nabble.com.
---
It looks like you have the same for both your header
and your footer. I'm not sure if this is causing your problem or not, but I
do know that JSF requires that id be unique.
Let me know if this fixes the problem or not. Otherwise I have an
environment setup that I can try to duplicate the erro
