> -----Original Message----- > From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Sent: Friday, August 09, 2013 10:47 AM > To: Tomcat Users List > Subject: Re: Upgrade to Tomcat 7 Issues > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Chuck, > > On 8/9/13 10:08 AM, Caldarale, Charles R wrote: > >> From: Seema Patel [mailto:seema...@hotmail.com] Subject: RE: > >> Upgrade to Tomcat 7 Issues > > > >> In my WEB-INF/lib I have the following (sorry the list is quite > >> long): activation.jar > > > >> In Tomcat7.0/lib directory I have (I have grouped them > alphabetically > >> so it doesn't make the list too long downwards, like the above list) > > > >> activation.jar j2ee.jar > > > > You must never, never, never have the same class files in multiple > > locations in the class loader hierarchy (e.g., activation.jar and > > several others). > > I don't think "activation" is something provided by servlet containers. > I don't see it in a stock Tomcat, for example. >
CAVEAT: I have yet to verify this via testing, but.... I was reading the documentation on the javamail api and discovered that as of Java 6, the activation.jar file that was previously required in Java 5 and below is no longer needed, as the functionality is provided in the Java 6&up jvm. Now I'm not sure what that means overall, but for myself, and many others, the only reason we included activation.jar in our apps is to support javamail. If you are using activation.jar features directly, I would suggest verifying if you still need the jar file after upgrading jvms, otherwise, it should be safe to delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
