[
https://issues.apache.org/struts/browse/TILES-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cserveny Tamás updated TILES-220:
---------------------------------
Attachment: 2.0.5.patch
This is a patch against 641026.
Maybe we could drop the factory, and just leave the
WildcardMatchingDefinitions, thus other factories could take advantage of the
wildcard matching.
Another aspect is, that this factory creates a reference to the XWork package.
I can't judge whether this is bad or not.
> [tiles] use of wildcard in tiles-defs.xml as for wildcard mappings
> ------------------------------------------------------------------
>
> Key: TILES-220
> URL: https://issues.apache.org/struts/browse/TILES-220
> Project: Tiles
> Issue Type: New Feature
> Components: tiles-core
> Affects Versions: 2.0.4
> Environment: Operating System: other
> Platform: Other
> Reporter: nicolas de loof
> Priority: Minor
> Fix For: 2.1.x
>
> Attachments: 2.0.5.patch, patch.txt, patch.txt, patch.txt,
> WildcardMatchingDefFactory.java
>
>
> Wildcard mappings is a interesting new feature in struts 1.2.x. This
> enhancement
> allow to use wildcard in tiles definition too like the following :
> <definition name="tiles:test.*" path="/testlayout.jsp">
> <put name="testName" value="{1}"/>
> <put name="def" value="tiles:another.definition.{1}" type="definition"/>
> </definition>
> Using this, you can build a full wildcard request handling when adding a
> mapping
> in struts-config :
> <action path="/Test*"
> forward="tiles:test.{1}"/>
> Please note : properties are replaced in attributes of the definition only for
> put elements. It may require a little bit more coding in
> DefinitionsFactory.getDefinition() to add putlist support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
