Since MMBase containts a class that depends on it (org.mmbase.module.JMSendMail), it should ship with mail.jar. Application servers may ship with it as well, but they're not required to.
Regarding the common/endorsed directory: it is not intended for this purpose. The correct location for thirdparty libraries is the webapp's WEB-INF/lib. Or alternatively Tomcat's shared/lib if you want to make it available to all webapps. See: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/class-loader-howto.html Rob van Maris Technical Consultant Quantiq xmedia & communication solutions Koninginneweg 11-13 1217 KP Hilversum T +31 (0)356257211 M +31 (0)651444006 E [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michiel Meeuwissen > Sent: woensdag 21 januari 2004 11:52 > To: [EMAIL PROTECTED] > Subject: mail.jar > > > Tomcat5 does, in contradiction to tomcat4, not ship mail.jar > anymore. Does anybody know what we should advice about this > in e.g. the releasenotes? > > Btw, when activating JMSendMail in tomcat5: > 11:34:05,030 SER 8589 kb org.mmbase.module.Module > loadModulesFromDisk.380 - Loading module sendmail with class > org.mmbase.module.JMSendMail 11:34:05,037 ERR 8664 kb > org.mmbase.servlet.MMBaseServlet error.74 - Could not find > module with name 'MMBASEROOT'! 11:34:05,045 ERR 7335 kb > org.mmbase.servlet.MMBaseServlet error.74 - > javax/mail/MessagingExceptionjavax/mail/MessagingException > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:141) > at > org.mmbase.module.Module.loadModulesFromDisk(Module.java:390) > at org.mmbase.module.Module.getModule(Module.java:322) > at org.mmbase.module.core.MMBase.getMMBase(MMBase.java:544) > at > org.mmbase.servlet.MMBaseServlet.init(MMBaseServlet.java:168) > at > org.mmbase.servlet.BridgeServlet.init(BridgeServlet.java:188) > > > it can be solved by placing mail.jar in <tomcat>/common/endorsed.
