struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Husted <>
Subject Re: Terminology: modules versus sub-apps
Date Thu, 17 Oct 2002 10:31:11 GMT
I'm not exactly sure of what we all are thinking of. Organizing large and/or multilingual applications
is a big 
topic, and there would be lots of different ways to go here. 

The idea with the sub-application modules is to simply add one more layer of nesting under
the application 
context. This makes it easy to take two applications that were developed independantly and
clunk them together 
-- like portlets. Another consequence of modules is that it gives you extra sets of struts-config.xml's
to work 
with that automatically have their own namespace. In effect, it puts "Chinese Walls" between
your developers so 
they don't step on each other. 

Of course, there are other ways to organize modules. Another would be to nest or scope modules,
like Locales, so 
that more specific configurations each inherits elements from more general configurations.
I do know teams that 
use this sort of approach to customize a single applications for various clients and also
to provide role-based 

Perhaps as an adjunct to Steve's roadmap we can open documents where we can start to enumerate
the various 
approaches for future study, inlcuding this one. 


10/16/2002 9:34:48 PM, "Peter A. J. Pilgrim" <> wrote:
>At the mo, I understand that there is just one level of sub applications
>that can work reasonably well e.g "config/sub1", "config/sub2" and you
>guys (and gals) are thinking of extending this to its natural conclusion
>then I might suggest that maybe you take a leaf from "Log4J" categories.
>* define arbitary tree paths and nodes.
>* define arbitary struts "category" that you can always get the root from.
>Have I bitten off more than I can chew or barking up the wrong tree?
>Peter Pilgrim
>ServerSide Java Specialist
>My on-line resume and for interview videos about myself, J2EE
>Open Source, Struts and Expresso.
>    ||
>    \\===>  `` ''
>To unsubscribe, e-mail:   <>
>For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message