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
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
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:
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
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
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
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
