Not sure how much this helps, but it works for us. I have the same dependencies in a parent pom for the webapps we have, and I specify '<scope>provided</scope>'. This keeps them out of the lib directory. The manifest classpath is not being set in the webapps. Only in the ejb's. To be honest, my j2ee spec understanding is a little light here. It seems like the ejbs need the cp in the manifest, but the wars are ok without. Of course, we're on weblogic 7 still, so we're all over the place with sticky issues.
On 3/23/06, Peschier J. (Jeroen) <[EMAIL PROTECTED]> wrote: > > > Yes, classloader issues arise. Duplicate JARs in the EAR and WAR are > treacherous! Consider this scenario: > - JAR dependency contains common class with static fields > - WAR depends on said common class > - SAR depends on said common class > > If the JAR is packaged in both the EAR and the WAR, the static fields > cannot be shared since the WAR has its own classloader. This makes the > WAR indeed deployable outside the EAR but in many cases it is not what > you want. > > > -----Oorspronkelijk bericht----- > Van: Richard Sladek [mailto:[EMAIL PROTECTED] > Verzonden: donderdag 23 maart 2006 13:43 > Aan: [email protected] > Onderwerp: Re: M2 - Best practice for common jars between EJB,WAR > modules in EAR > > I have just one more question: > might such duplicates in ear modules cause some classloader issues (or > anything) or is it completely safe to have them? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
