You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2007/09/13 20:40:36 UTC

[jira] Commented: (STR-2990) doesn't change module scope when including a different module action result forward

    [ https://issues.apache.org/struts/browse/STR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42192 ] 

Antonio Petrelli commented on STR-2990:
---------------------------------------

I think that we need a test case, so we can debug it.
Ignacio, could you provide a simple test case for it?

> <tiles:insert> doesn't change module scope when including a different module action result forward
> --------------------------------------------------------------------------------------------------
>
>                 Key: STR-2990
>                 URL: https://issues.apache.org/struts/browse/STR-2990
>             Project: Struts 1
>          Issue Type: Bug
>          Components: Tiles 1 Plugin
>    Affects Versions: 1.3.5
>         Environment: JDK 5 / JDK 6, Struts 1.3.5
>            Reporter: Ignacio de Córdoba
>
> If you insert the forward result of an action:
> <tiles:insert attribute="userservice"/> which maps to a page that has an <html:form>, if userservice is an attribute mapping to a page or action in a different module as current action's module, <html:form> will never find corresponding action, as the page is for the external module, but struts considers we are in current module.
> As tiles can have common tiles definitions, maybe an extra parameter to <tiles:insert> is needed, to specify that supplied attribute is to be rendered in a different module scope (¿<tiles:insert attribute="userservice" module="/user"/>?) Or just make tiles detect module using the attribute path.

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