Cedric Dumoulin wrote:
In fact, I have already think about how to make Tiles more "modules/sub-apps" compliant. I haven't solved this question, because there is some opposite views: modules are intended to clearly separate works (the Ted's "chinese wall"), and Tiles are intended to avoid duplications by allowing sharing of common jsp.
Of course, we can conciliate both, but this require some thinking:
* A tiles configuration file requires some references to common
URLs and to common definitions. o How to distinguish between an URL from the module namespace
and an URL from another namespace (common, root or other
module), without overloading too much the configuration file ?
Must admit I favour one level of Modules, because it makes sense. You may want to have many modules (different applications) to share the same web application context. I also favour in that case separate namespaces but there should be a get out clause or API hook which allows developer to get to the default Module if required. This would help us with Expresso, which would be for us always the default Module.
I cannot see the reason for Modules of Modules of Modules ad infinitum. Why? -- Peter Pilgrim ServerSide Java Specialist My on-line resume and for interview videos about myself, J2EE Open Source, Struts and Expresso. || \\===> `` http://www.xenonsoft.demon.co.uk/no-it-striker.html '' -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
