Hello,
We're looking at unifying three existing standalone struts applications
into one core struts application with two modules. We'd like the modules
to remain as autonomous as possible so that we could replace or make one
of them stand on it's own again in the future.
My question is how to layout the projects:
coreApp/
moduleA/
moduleB/
WEB-INF/
classes/
lib/
Under moduleA/ and moduleB/ can I also have a complete WAR file layout
with WEB-INF/ and pages/ classes/ etc? If not it would appear that the
modules end up getting pretty mixed together. Of course we use Ant and
our development layouts use common J2SE conventions, but without
WEB-INF/ and pages/ classes/ etc dirs under the modules we loose the
ability to point a server context at a developers environment, so that
they can work on a module independently. True?
We would like to move to one shared session across the applications.
That's the impetus for moving to modules. However, the autonomy
compromise might be too great. That's my fear.
--------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does
not waive confidentiality or privilege, and use is prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
