Well, i am using weblogic 5.1, which seems to be the most ignorant servlet container I have ever used. It requires explicit paths to EVERY class, so I have to reference the root of my packages (i.e. WEB-INF/classes) and EVERY individual jar file that needs to be referenced at run time, even if they are placed in WEB-INF/lib. Normally I would leave things as is, but my classpath is rediculous as is, and it seems like all these jars combined with replaced about eight individual entries with one commons-*.jar file.
Do you follow my logic? Jason -------Original Message------- From: Chris Trawick <[EMAIL PROTECTED]> Sent: 02/21/03 08:46 AM To: Struts Users Mailing List <[EMAIL PROTECTED]> Subject: Re: Re: combining commons-*.jar > > What is cleaning up the classpath about anyway? For building? Ant takes care of that, just use a lib directory. For deployment? Try /WEB-INF/lib or use your container's libdir. Coupling all the commons products together violates their designed modularity and introduces bloat. I personally don't have warm fuzzies about bundling 8 megs of fluff with every war and passing it around between different servers. It especially gets in the way of JBoss, when a large transfer (even just filesystem-to-filesystem) can cause the deployer to hose itself by trying to load the thing before it's actually there. Then again, maybe your situation is different... chris ----- Original Message ----- From: "Jason Vinson" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 8:33 AM Subject: Re: Re: combining commons-*.jar > So if there was an upgrade, i could just rebundle them all correct? If that's the only drawback, I think I may go ahead and combine them. Anyone else care to comment? > > Jason > > > -------Original Message------- > From: Ian Hunter <[EMAIL PROTECTED]> > Sent: 02/21/03 08:32 AM > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: Re: combining commons-*.jar > > > > > If one component was upgraded, you'd have to replace the whole shootin' > match. > > ----- Original Message ----- > From: "Jason Vinson" <[EMAIL PROTECTED]> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Sent: Friday, February 21, 2003 8:28 AM > Subject: combining commons-*.jar > > > > This may be a dumb question, but is there any reason to not combine all > the commons-*.jar libraries into one jar file? I am attempting to clean > up > our server's classpath, and combining all these jars would really help > out. > > > > TIA, > > Jason > > > > --------------------------------------------------------------------- > > 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] > > > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
