[
https://issues.apache.org/struts/browse/TILES-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45613#action_45613
]
SYPECom Inc. commented on TILES-363:
------------------------------------
It seems I misunderstood your request, as I thought you were referring to my
CONTEXT and not my REQUEST. The context I described (500+ definitions) is
unavoidable in our project (transitioning from legacy code, and having very
specific functional requirements), and so that context cannot change. The
preparer we are using on all these tiles is required to add a kind of smart
logic to determine how to apply (or not) a tile attribute's default value for
each request (thus avoiding the need to add that logic code to the underlying
JSP files).
So, my request for enhancement is really only about adding a way of specifying
"global" preparers within a definitions file. Much like it is possible to
define default interceptors and global results in Struts2.
Thank you!
> Attaching global preparer to a <tiles-definitions> list
> -------------------------------------------------------
>
> Key: TILES-363
> URL: https://issues.apache.org/struts/browse/TILES-363
> Project: Tiles
> Issue Type: New Feature
> Affects Versions: 2.1.2
> Environment: Using Tiles 2.1.2
> Reporter: SYPECom Inc.
> Priority: Minor
>
> CONTEXT: one of the definitions file I am working on has 500+ definitions,
> and all of them require the same preparer.
> REQUEST: The XML would be much lighter and cleaner if it were possible to
> attach a preparer to the single <tiles-definitions> element (that would apply
> to all nested definitions) instead of to each <tiles-definition> element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
