In the regular scheme of things, when, for example, an Action returns an ActionForward, the request processor lets Tiles have a look at the forward, so that it can handle the case where a path is a Tile rather than a genuine path. Unfortunately, this doesn't happen in all cases, specifically in the new world of Chain and the composable request processor.
For example, when the path in an <exception> definition is followed, Tiles doesn't get a chance to play in the game. This is because Tiles only gets to play after ExecuteAction succeeds. In this particular case, I believe that inserting the TilesPreProcessor command in the middle of the 'servlet-exception' chain will do the trick. However, before making this change (and testing it ;), I wanted to ping the list to see if there are other scenarios that people can come up with in which this kind of thing might happen. Is this just a one-off bug, or do we have a bigger issue with getting Tiles into play in all the right places? -- Martin Cooper --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
