As far as i understand, all of the app must be deployed in the same war file: I dont think an app can be split between war files (please correct me if i'm wrong here!).
If you can split an app, then i doubt struts would be bothered. With our webapps we make use of cvs, and for deployment checkout the whole thing, and build it, deploy it, restart app server all automatically. Note also that you dont have to package a webapp using a war file... i dont Just copying the directory strusture into a folder in webapps is certainly much easier for development. Daniel. > -----Original Message----- > From: Brian Styles [mailto:[EMAIL PROTECTED] > Sent: 19 May 2004 16:38 > To: [EMAIL PROTECTED] > Subject: RE: Modular packaging of a large application > > > Hi Daniel, > > thanks for the reply. > > That's fine for development but what about deployment though? > Will all the > modules have to be deployed in a single war file so they can see > each other? > > > >From: "Daniel Perry" <[EMAIL PROTECTED]> > >Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > >To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > >Subject: RE: Modular packaging of a large application > >Date: Wed, 19 May 2004 16:18:17 +0100 > > > > > > > 1) Should all my entity beans be packaged in a single jar? > > > > > > >no idea... i dont go in for the session beans/entity beans, i'm > using OJB > >so > >it's a bit different. > > > > > 2) Different modules will probably mean different session beans, jsps > >and > > > struts actions. > > > > > > >This is no problem. Different modules all have their own config > file, so > >as > >long as the action classes/jsps dont overlap there wont be a problem. I > >would suggest you put the action classes for different modules > in different > >packages, and jsps in different folders. That way, development can be as > >independant as you like. > > > >Daniel. > > > > > > > -----Original Message----- > > > From: Brian Styles [mailto:[EMAIL PROTECTED] > > > Sent: 19 May 2004 15:30 > > > To: [EMAIL PROTECTED] > > > Subject: Modular packaging of a large application > > > > > > > > > Hi everyone, > > > > > > I've built an application in a standard j2EE format > > > > > > JSPs-->Struts-->Session Beans-->CMR Entity Beans. > > > > > > This is deployed in an exploded ear, with struts and JSPs in the > > > war as well > > > as the session bean interfaces. Then I have the Session Beans and > > > CMR Entity > > > Beans in a jar. > > > > > > Now I want to go to a larger environment where different > developers are > > > working on different modules, yet I still want each module to be > > > accessable > > > through a single point - ie, struts. > > > > > > Struts 1.1 has the concept of modules, allowing different > struts config > > > files per module, however, from the context of deployment I have some > > > worries. > > > > > > 1) Should all my entity beans be packaged in a single jar? > > > > > > 2) Different modules will probably mean different session beans, jsps > >and > > > struts actions. > > > > > > Therefore, I would really appreciate advice/experienc on > packaging up an > > > architecture like this. > > > > > > regards, > > > Brian > > > > > > _________________________________________________________________ > > > The new MSN 8: advanced junk mail protection and 2 months FREE* > > > http://join.msn.com/?page=features/junkmail > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > _________________________________________________________________ > The new MSN 8: advanced junk mail protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
