Yes, it works this way for javax.mail.Session too. You need to put mail.jarand activation.jar in lib/common so as you can find the Session from JNDI.
On 5/6/05, Michael Echerer <[EMAIL PROTECTED]> wrote: > > Ron Heeb wrote: > > my understanding comes from this book i got: 'common is responsible for > > classes that are used by Tomcat and publicly available to all Web > > apps'. shared is like common, except that 'developers can place their > > own classes and JAR files into the shared class loader domain'. > > developers shouldn't put anything into common. this is from > > Professional Apache Tomcat 5 from Wrox. for what it's worth...ron > > > You need "common/lib" e.g. for JDBC drivers. Because if you want to > configure a JNDI Datasource and use Tomcats Jakarta Commons DBCP > connection pool there's "no" other way then placing the <driver>.jar > into common/lib because Tomcat itself requires the classes already, not > only your webapps. > > Moreover you should make sure that the webapps don't contain the > driver.jar in that case again. > Otherwise you'll face lot's of funny classloading issues... > E.g. if you work with driver specific data types you could face problems > like "instanceof" returning false although using the same class because > objects might be loaded by different classloaders (and instanceof and > casting only works within the same classloader). > > Cheers, > Michael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
