You'll have to define them in each app for now :-( I have this exact
same situation.
1.1 final will be all about seperatism of modules (each module will
behave like it's own independent application). The idea is that, this
being the first release with modules, we should first learn how to make
modules behave well independently - and gain user feedback - and then
(possibly - based off user feedback and how modules are being used) add
some sharing of some form in later (incrementally in 1.2.x releases).
A shared configuration (in some form or other) *may* be in 1.2.0, but it
will *not* be in 1.1 final. I'm sorry - I feel your pain. For now
you'll have to replicate them.
Peterkofsky, Don wrote:
We have what should be a fairly common situation: several sub-applications
corresponding to different business unit functions, and a global navigation
header that navigates among these different sub-applications (Unit1,
Unit2, etc.). The navigation header is defined in a global template, and so
the links to the different sub-applications need to be specified once in the
template page.
So, the question is, can the actions or forwards that specify the targets
for the sub-applications be specified in a single place (like the default
struts app in struts-config.xml) or a special common struts app (like
struts-comon-config.xml)? Or, must the forwards/actions be specified in
each of the sub-apps configs (struts-Unit1-config.xml,
struts-Unit2-config.xml)?
I would not like to have to copy/paste the common/global resources into each
sub-application; I would like to be able to access a resource defined in a
common config or any sub-app config, from within any other sub-app, without
having to define anything particular in the sub-app -- i.e., like
html:rewrite forward=/Unit2/HomePage / from within Unit2 sub-app. Is
there any known way to do what I'm looking for?
--
Eddie Bush
--
To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
