[
https://issues.apache.org/jira/browse/TILES-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076261#comment-13076261
]
David Hay commented on TILES-534:
---------------------------------
Changing PatternUtil line 227 from 'replaceFirst' to 'replace' appears to solve
the problem. In addition, it avoids the Pattern compile for each replacement.
> Wildcarding interferes with EL Expressions in put-attribute
> -----------------------------------------------------------
>
> Key: TILES-534
> URL: https://issues.apache.org/jira/browse/TILES-534
> Project: Tiles
> Issue Type: Bug
> Components: tiles-core, tiles-el
> Affects Versions: 2.2.2
> Reporter: David Hay
>
> I'm trying to create a Tiles definition that uses wildcards (regex) as well
> as an EL expression. It appears that the placeholder replacement for
> wildcards is interpreting the EL expression as an invalid placeholder instead
> of leaving it alone. This looks to be related to TILES-502.
> I've created the pattern definition resolver and EL expression support as
> described on the websit
> (http://tiles.apache.org/framework/tutorial/advanced/wildcard.html and
> http://tiles.apache.org/framework/tutorial/advanced/el-support.html,
> respectively). My tiles definition looks like the following:
> <definition name="REGEXP:(.*)Body" template="/WEB-INF/jsp/{1}/index.jsp">
> <put-attribute name="pageContent"
> expression="EL:/WEB-INF/jsp/${website.template.name}/${currentPage.name}.jsp"/>
> </definition>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
