mail.jar, activation.jar and classloading
What is special about mail.jar (and activation.jar) that requires putting them into the common.loader? Quote from the Tomcat docs: Unpackage the distribution(s) and place mail.jar (and activation.jar if required) into $CATALINA_HOME/lib so the JAR(s) is(are) available to Tomcat during the initialization of the mail Session Resource. http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html This question is spawned by a recent thread on the Ant mailing list, where the same question was raised in the context of classloading issues, but not answered. Mail task with mail.jar activation.jar out of lib folder http://ant.markmail.org/thread/ojjm7g5otejua33i Thanks. -- Michael Ludwig - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mail.jar, activation.jar and classloading
On Wed, 26 Jan 2011 11:52:04 +0100, Michael Ludwig mil...@gmx.de wrote: What is special about mail.jar (and activation.jar) that requires putting them into the common.loader? Any objects you want have access to via JNDI, have to be accessible by tomcat in order to create them. That means they should be located in common classloader. -- Mikolaj Rydzewski m...@ceti.pl - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mail.jar, activation.jar and classloading
For the record: JAF (activation.jar) is already in Java 6 (and that sucks :-)). Op woensdag, 26 januari 2011 11:52 schreef Michael Ludwig mil...@gmx.de: What is special about mail.jar (and activation.jar) that requires putting them into the common.loader? Quote from the Tomcat docs: Unpackage the distribution(s) and place mail.jar (and activation.jar if required) into $CATALINA_HOME/lib so the JAR(s) is(are) available to Tomcat during the initialization of the mail Session Resource. http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html This question is spawned by a recent thread on the Ant mailing list, where the same question was raised in the context of classloading issues, but not answered. Mail task with mail.jar activation.jar out of lib folder http://ant.markmail.org/thread/ojjm7g5otejua33i Thanks. -- Michael Ludwig - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mail.jar, activation.jar and classloading
Ronald Klop schrieb am 26.01.2011 um 12:08 (+0100): For the record: JAF (activation.jar) is already in Java 6 (and that sucks :-)). It might (I don't know). Mail.jar, however, isn't in Java 6 SE. And from the discussion on the Ant list it appeared that there was something special about this jar that requires special classloader treatment. Mail task with mail.jar activation.jar out of lib folder http://ant.markmail.org/thread/ojjm7g5otejua33i -- Michael Ludwig - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mail.jar, activation.jar and classloading
Mikolaj Rydzewski schrieb am 26.01.2011 um 12:07 (+0100): On Wed, 26 Jan 2011 11:52:04 +0100, Michael Ludwig mil...@gmx.de wrote: What is special about mail.jar (and activation.jar) that requires putting them into the common.loader? Any objects you want have access to via JNDI, have to be accessible by tomcat in order to create them. That means they should be located in common classloader. Thanks. So nothing intrinsically special about mail.jar itself? -- Michael Ludwig - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mail.jar, activation.jar and classloading
On Wed, 26 Jan 2011 12:24:58 +0100, Michael Ludwig mil...@gmx.de wrote: Mikolaj Rydzewski schrieb am 26.01.2011 um 12:07 (+0100): On Wed, 26 Jan 2011 11:52:04 +0100, Michael Ludwig mil...@gmx.de wrote: What is special about mail.jar (and activation.jar) that requires putting them into the common.loader? Any objects you want have access to via JNDI, have to be accessible by tomcat in order to create them. That means they should be located in common classloader. Thanks. So nothing intrinsically special about mail.jar itself? Nothing I'm aware of. You can place it in WEB-INF/lib but you won't be able to retrieve mail session from JNDI. -- Mikolaj Rydzewski m...@ceti.pl - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mail.jar, activation.jar and classloading
2011/1/26 Michael Ludwig mil...@gmx.de: What is special about mail.jar (and activation.jar) that requires putting them into the common.loader? Quote from the Tomcat docs: Unpackage the distribution(s) and place mail.jar (and activation.jar if required) into $CATALINA_HOME/lib so the JAR(s) is(are) available to Tomcat during the initialization of the mail Session Resource. http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html This question is spawned by a recent thread on the Ant mailing list, where the same question was raised in the context of classloading issues, but not answered. It just says that you need to get those jars by yourself. I have not verified the following, but I suspect that it is because of their license. Mail task with mail.jar activation.jar out of lib folder http://ant.markmail.org/thread/ojjm7g5otejua33i Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
