Well, usually a WAR is a composite collection of JSPs, classes, deployment descriptor, third-party jars and so on. If you have people who write classes, they can create a jar, not a war, and people who create JSP can just place them in the correct location. A good build project could then merge the classes, the JSPs and whatever needed in a single, composite, war file. Need to change a behaviour? Modify the class and redeploy the application. Need to change layout? Change the JSP and copy/redeploy to the correct location (Additionally restart the server :)
My 2 cents, Marco ----- Original Message ----- From: "Ulrich Mayring" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 08, 2003 10:25 AM Subject: Re: How to use classes from another webapp/context? > Christopher Williams wrote: > > > > Unfortunately, you do need to move classes common to multiple web apps into > > library files. You don't have to put the library files into common\lib, > > however. You can put the JARs in WEB-INF/lib inside your WAR file. Never > > done it myself, but it's supposed to work. > > Yep, but then I can't deploy/undeploy the two WARs seperately. We have > developers, who write classes, and they want to manage their WAR, and we > have people, who write JSP files, and they want to manage their own WAR. > But it seems they can't work together in the way I imagined. > > Thank you very much for your help, > > Ulrich > > > > --------------------------------------------------------------------- > 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]
