Craig R. McClanahan wrote:
>
> On Wed, 16 Oct 2002, Ted Husted wrote:
>
>
> Don't have time to dive into the substantive technical details today, but
> in general I'm OK with a strategy of comma-delimited list of
> struts-config.xml resource files used to configure a single app module
> (consistent with the Tiles and Validators styles). I presume this just
> means running as many Digester.parse() calls as you need, and no other
> fundamental changes, right?
>
> Craig
As a core contributor for Expresso Framework I find this discussion interesting.
In Expresso one of the contributors put together a XML Augmentator that parse
several XML configuration files. We integrated Struts 1.0.2 so we do not have
a special notation of sub applications, but just the one struts-config file, but
we can have several *expresso-struts-config* files.
If the expresso-strut config implement the same XML DTD then in theory they can
merged together internally in a giant DOM. This is what I think the contribotor
( Mike Rimov, I think) did for Expresso. I am not sure how it solves the modules
problem though in pure Struts.
I have a little difficult understanding the terminology here.
Is a module the same as a subapplication?
I can see a might have a little bit work ahead of me, when I start trying to
integrate Struts 1.1 with the latest Expresso if I do not under all the
sub application issues.
For Expresso it will make sense to subapplications to know about the default
application (which is in our case Expresso). A sub application should be able
to find out about sub applications also loading into the system. But hey may be
I am way of base here. TRYING TO KEEP TEXT SHORT, TOO MUCH STRAIN ON MY EYES.
--
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:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
