I found the answer myself ; Here it is:
You do not need to specify in your struts config file(s) that the processorClass will be TilesRequestProcessor. This is automatically done by the plug-in. If a class is specified in the struts configuration file(s), that processorClass will be used instead. Which means ( as I believe it does ), that only if I extend TilesRequestProcessor for my own purposes, I need to add the controller configuration. If not, it will perfectly fine using the default (which is TilesRequestProcessor) setting from the plugin. Ergo, my friend is wrong, I do not HAVE TO set the controller explicitly to TilesRequestProcessor... rgds albi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 01, 2005 2:52 PM To: user@struts.apache.org Subject: TilesRequestProcessor I think I'm missing the point of the TilesRequestProcessor .... I have a few simple tiles in a project with to modules (default & crud). Actually the default uses tiles and the other one doesn't. Now, the tiles in the default module seem to work just fine, but a friend told me, that I would need to define the TilesRequestProcessor in a controller tag in the default module. Adding this tag doesn't seem to change anything. Can some explain to me why that should be done? Rgds albi --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
