[
https://issues.apache.org/jira/browse/TILES-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated TILES-574:
--------------------------------
Description:
Using tiles 3.0.1 w. Spring 3.2.4 I am trying to use an multiple expressions
that include a wildcard:
{code}
<definition name="*.container" extends="base.container.layout">
<put-list-attribute name="commonContainerScripts" cascade="true">
<add-attribute
expression="resources/${buildVersion}/scripts{1}/startup${minType}.js" />
</put-list-attribute>
</definition>
{code}
the first variable buildVersion resolves correctly. \{1} also resolves
correctly, however if minType appears after \{1}, minType resolves to
buildVersion. If I move minType in my expression to before \{1}, then it
resolves properly.
was:
Using tiles 3.0.1 w. Spring 3.2.4 I am trying to use an multiple expressions
that include a wildcard:
<definition name="*.container" extends="base.container.layout">
<put-list-attribute name="commonContainerScripts" cascade="true">
<add-attribute
expression="resources/${buildVersion}/scripts{1}/startup${minType}.js" />
</put-list-attribute>
</definition>
the first variable buildVersion resolves correctly. {1} also resolves
correctly, however if minType appears after {1}, minType resolves to
buildVersion. If I move minType in my expression to before {1}, then it
resolves properly.
> Tiles expressions do not work after wildcard
> --------------------------------------------
>
> Key: TILES-574
> URL: https://issues.apache.org/jira/browse/TILES-574
> Project: Tiles
> Issue Type: Bug
> Components: tiles-el, tiles-extras, tiles-servlet-wildcard
> Affects Versions: 3.0.1
> Environment: Windows 7, Tomcat 6, Java 1.6, Spring 3.2.4
> Reporter: Stephen Parker
> Assignee: Mck SembWever
>
> Using tiles 3.0.1 w. Spring 3.2.4 I am trying to use an multiple expressions
> that include a wildcard:
> {code}
> <definition name="*.container" extends="base.container.layout">
> <put-list-attribute name="commonContainerScripts" cascade="true">
> <add-attribute
> expression="resources/${buildVersion}/scripts{1}/startup${minType}.js" />
> </put-list-attribute>
> </definition>
> {code}
> the first variable buildVersion resolves correctly. \{1} also resolves
> correctly, however if minType appears after \{1}, minType resolves to
> buildVersion. If I move minType in my expression to before \{1}, then it
> resolves properly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
