On 10/25/06, David H. DeWolf <[EMAIL PROTECTED]> wrote:
Greg Reddin wrote: > > On Oct 24, 2006, at 3:23 AM, Antonio Petrelli wrote: > >> Now the question is: Why do you need multiple >> TilesApplicationContexts? Just curious :-) > > I think David was asking the same question. If Tiles is deployed in a > common classloader (i.e. Tomcat's common/lib directory) you'd want each > application to have its own TilesApplicationContext since each > application would have its own instances of the internal components > wrapped by TilesApplicationContext. That just sounds like more trouble > than it's worth supporting IMO :-) But, inevitably somebody will plunk > the tiles JAR down in common/lib and start hollering about things not > working. So we should probably at least document the issues with it. > Exactly: the only reason you'd need more than one would be when someone tries to get fancy and use common/lib. MHO is that not only is it more trouble than it's worth - using common/lib for a webapp library is also something we should discourage. Providing documented "non-support" is definitely a form of discouragement :)
Yep, the more we can discourage this kind of thing, the better. It'll save everyone touble in the long run. -- Martin Cooper I'll go ahead and refactor to support only one TilesApplicationContext
and then move forward with the configurabality feature. > Greg > > > > > --------------------------------------------------------------------- > 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]
