Jim Crossley wrote:
> I'm now beginning to think that what I really need is a Controller, so
> I'm going to focus my efforts there for now. The docs mention that a
> Controller could be implemented as a Struts action. Does that require
> the Action to implement the Controller interface or is there some
> Tiles magic that occurs merely by setting the controllerClass
> attribute in the definition?
There is some magic. Tiles check whether you use Action or Controller interface.
If you use Action, it will wrap it with a Controller interface.
Also you can put the url of your Struts action as controller, with no change to
the action <tiles:insert ... controllerUrl="action.do" />.
My prefer way is to extends TilesAction (which itself extends struts action), and
implements the new perform() which provide an extra parameter (the tile context !).
Cedric
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
