You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Victor Voronenko (JIRA)" <ji...@apache.org> on 2008/03/24 15:38:58 UTC

[jira] Created: (WW-2562) Only first action with result type="XSLT" included in JSP by is executed; the rest is ignored

Only first action with result type="XSLT" included in JSP by <s:action> is executed; the rest is ignored
--------------------------------------------------------------------------------------------------------

                 Key: WW-2562
                 URL: https://issues.apache.org/struts/browse/WW-2562
             Project: Struts 2
          Issue Type: Bug
    Affects Versions: 2.0.11
         Environment: Windoes XP/SP2; WebSphere Application Server v6.1.0.7
            Reporter: Victor Voronenko


Declare two actions with result type="xslt".
<action name="action1" class="someAction1">
	<result type="xslt" name="success"/>
</action>
<action name="action2" class="someAction2">
	<result type="xslt" name="success"/>
</action>

and one action with default result type:
<action name="DealSearch">
<result name="success">/showResult.jsp</result>
</action>

In showResult.jsp include two <s:action> directives:
<s:action name="action1" executeResult="true"/>
<s:action name="action2" executeResult="true"/>

An issue: the second action will never be executed and its result never be included in output stream.
Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.

Unlike the type="xslt" it allows to include multiple actions with default result type.

Suggestion: the output stream might be flushed and closed after the 1st action's result set handled by Xalan.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WW-2562) Only first action with result type="XSLT" included in JSP by is executed; the rest is ignored

Posted by "Victor Voronenko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Victor Voronenko updated WW-2562:
---------------------------------

    Description: 
Declare two actions with result type="xslt".
<action name="action1" class="someAction1">
	<result type="xslt" name="success"/>
</action>
<action name="action2" class="someAction2">
	<result type="xslt" name="success"/>
</action>

and one action with default result type:
<action name="DealSearch">
<result name="success">/showResult.jsp</result>
</action>

1. Include two <s:action> tags in showResult.jsp :
<s:action name="action1" executeResult="true"/>
<s:action name="action2" executeResult="true"/>

2. Run DealSearch action.

The issue is: the second action ("action2") will never be executed and its result never be included in output stream.
Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.
The problem does not depend on whether XSL template specified or not.

Unlike with type="xslt"  actions with default result type included by <s:action> are free from this problem.

Suggestion: output stream might have been flushed and closed after handling the 1st action's result set.

  was:
Declare two actions with result type="xslt".
<action name="action1" class="someAction1">
	<result type="xslt" name="success"/>
</action>
<action name="action2" class="someAction2">
	<result type="xslt" name="success"/>
</action>

and one action with default result type:
<action name="DealSearch">
<result name="success">/showResult.jsp</result>
</action>

1. Include two <s:action> tags in showResult.jsp :
<s:action name="action1" executeResult="true"/>
<s:action name="action2" executeResult="true"/>

2. Run DealSearch action.

The issue is: the second action ("action2") will never be executed and its result never be included in output stream.
Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.
The problem does not depend on weather XSL template specified or not.

Unlike with type="xslt"  actions with default result type included by <s:action> are free from this problem.

Suggestion: output stream might have been flushed and closed after handling the 1st action's result set.


> Only first action with result type="XSLT" included in JSP by <s:action> is executed; the rest is ignored
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WW-2562
>                 URL: https://issues.apache.org/struts/browse/WW-2562
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.0.11
>         Environment: Windoes XP/SP2; WebSphere Application Server v6.1.0.7
>            Reporter: Victor Voronenko
>
> Declare two actions with result type="xslt".
> <action name="action1" class="someAction1">
> 	<result type="xslt" name="success"/>
> </action>
> <action name="action2" class="someAction2">
> 	<result type="xslt" name="success"/>
> </action>
> and one action with default result type:
> <action name="DealSearch">
> <result name="success">/showResult.jsp</result>
> </action>
> 1. Include two <s:action> tags in showResult.jsp :
> <s:action name="action1" executeResult="true"/>
> <s:action name="action2" executeResult="true"/>
> 2. Run DealSearch action.
> The issue is: the second action ("action2") will never be executed and its result never be included in output stream.
> Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.
> The problem does not depend on whether XSL template specified or not.
> Unlike with type="xslt"  actions with default result type included by <s:action> are free from this problem.
> Suggestion: output stream might have been flushed and closed after handling the 1st action's result set.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WW-2562) Only first action with result type="XSLT" included in JSP by is executed; the rest is ignored

Posted by "Victor Voronenko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Victor Voronenko updated WW-2562:
---------------------------------

    Description: 
Declare two actions with result type="xslt".
<action name="action1" class="someAction1">
	<result type="xslt" name="success"/>
</action>
<action name="action2" class="someAction2">
	<result type="xslt" name="success"/>
</action>

and one action with default result type:
<action name="DealSearch">
<result name="success">/showResult.jsp</result>
</action>

1. Include two <s:action> tags in showResult.jsp :
<s:action name="action1" executeResult="true"/>
<s:action name="action2" executeResult="true"/>

2. Run DealSearch action.

The issue is: the second action ("action2") will never be executed and its result never be included in output stream.
Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.
The problem does not depend on weather XSL template specified or not.

Unlike with type="xslt"  actions with default result type included by <s:action> are free from this problem.

Suggestion: output stream might have been flushed and closed after handling the 1st action's result set.

  was:
Declare two actions with result type="xslt".
<action name="action1" class="someAction1">
	<result type="xslt" name="success"/>
</action>
<action name="action2" class="someAction2">
	<result type="xslt" name="success"/>
</action>

and one action with default result type:
<action name="DealSearch">
<result name="success">/showResult.jsp</result>
</action>

In showResult.jsp include two <s:action> directives:
<s:action name="action1" executeResult="true"/>
<s:action name="action2" executeResult="true"/>

An issue: the second action will never be executed and its result never be included in output stream.
Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.

Unlike the type="xslt" it allows to include multiple actions with default result type.

Suggestion: the output stream might be flushed and closed after the 1st action's result set handled by Xalan.


> Only first action with result type="XSLT" included in JSP by <s:action> is executed; the rest is ignored
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WW-2562
>                 URL: https://issues.apache.org/struts/browse/WW-2562
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.0.11
>         Environment: Windoes XP/SP2; WebSphere Application Server v6.1.0.7
>            Reporter: Victor Voronenko
>
> Declare two actions with result type="xslt".
> <action name="action1" class="someAction1">
> 	<result type="xslt" name="success"/>
> </action>
> <action name="action2" class="someAction2">
> 	<result type="xslt" name="success"/>
> </action>
> and one action with default result type:
> <action name="DealSearch">
> <result name="success">/showResult.jsp</result>
> </action>
> 1. Include two <s:action> tags in showResult.jsp :
> <s:action name="action1" executeResult="true"/>
> <s:action name="action2" executeResult="true"/>
> 2. Run DealSearch action.
> The issue is: the second action ("action2") will never be executed and its result never be included in output stream.
> Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.
> The problem does not depend on weather XSL template specified or not.
> Unlike with type="xslt"  actions with default result type included by <s:action> are free from this problem.
> Suggestion: output stream might have been flushed and closed after handling the 1st action's result set.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WW-2562) Only first action with result type="XSLT" included in JSP by is executed; the rest is ignored

Posted by "Don Brown (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown resolved WW-2562.
---------------------------

    Resolution: Duplicate
      Assignee: Don Brown

Yep, this has been fixed by not closing the output stream

> Only first action with result type="XSLT" included in JSP by <s:action> is executed; the rest is ignored
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WW-2562
>                 URL: https://issues.apache.org/struts/browse/WW-2562
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.0.11
>         Environment: Windoes XP/SP2; WebSphere Application Server v6.1.0.7
>            Reporter: Victor Voronenko
>            Assignee: Don Brown
>
> Declare two actions with result type="xslt".
> <action name="action1" class="someAction1">
> 	<result type="xslt" name="success"/>
> </action>
> <action name="action2" class="someAction2">
> 	<result type="xslt" name="success"/>
> </action>
> and one action with default result type:
> <action name="DealSearch">
> <result name="success">/showResult.jsp</result>
> </action>
> 1. Include two <s:action> tags in showResult.jsp :
> <s:action name="action1" executeResult="true"/>
> <s:action name="action2" executeResult="true"/>
> 2. Run DealSearch action.
> The issue is: the second action ("action2") will never be executed and its result never be included in output stream.
> Same happens even when 2nd action has property executeResult="false" with <s:property> tag followed.
> The problem does not depend on whether XSL template specified or not.
> Unlike with type="xslt"  actions with default result type included by <s:action> are free from this problem.
> Suggestion: output stream might have been flushed and closed after handling the 1st action's result set.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.