Greg Reddin ha scritto:
Possible names could be:
* Controller for the class (or maybe TilesController) -
controllerClass and controllerUrl for tag attributes
Well, it's the controllerUrl I have the most trouble with. I don't
have any problem with declaring a class to be executed to prepare the
view. But an URL? An URL will always resolve to something - return a
response - and I don't think these view preparers should return
anything or resolve anything. They should simply be capable of
manipulating the context - preparing the context for the view (IMHO).
Last night (I should sleep, I know :-P ) I thought that "named
preparers" could be introduced.
I mean, instead of specifying the prepared class directly, they can be
configured in tiles-defs.xml through a <preparer> element (and
eventually in a <tiles:preparer> tag for page-scoped preparers) just
like definitions are configured, then a "preparer" attribute could be
added to <definition> and <tiles:definition> (and probably
<tiles:insert> too) specifying the name and not the class.
How does it sound to you?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
