On Oct 24, 2006, at 3:23 AM, Antonio Petrelli wrote:
David H. DeWolf ha scritto:
The one negative to this approach is that it will eliminate the
ability to support multiple contexts (when tiles is packaged in a
common classloader). The TilesUtil currently appears to be
implemented in a way which suggests that the original intent was
to support multiple contexts. That said, the support is already
only partial since Tiles utilizes several static accessors and
instances such as TilesUtilImpl will be shared across applications.
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.
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
