Bug 29255 - naming-factory.jar missing mail factories.
Summary: naming-factory.jar missing mail factories.
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 4
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 4.1.30
Hardware: All All
: P1 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-27 19:33 UTC by Yoav Shapira
Modified: 2004-11-15 12:52 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yoav Shapira 2004-05-27 19:33:38 UTC
The common/lib/naming-factory.jar is missing MailSessionFactory and 
SendMailFactory, making the javax.mail.Session JNDI functionality unavailable.
Comment 1 Yoav Shapira 2004-05-27 19:34:59 UTC
Note: as the classes themselves haven't changed in a couple of months, a quick 
workaround is to copy the naming-factory.jar from tomcat 5.0.24 into the 
common/lib directory of 5.0.25.
Comment 2 Yoav Shapira 2004-05-27 19:51:28 UTC
When I built 5.0.25, these two classes weren't compiled and therefore not 
included in the naming-factory.jar.  They weren't compiled because I didn't 
have javax.mail.Session in my libraries, making catalina/build.xml's 
${compile.javamail} condition evaluate to false.  It's too bad there's no way 
to grab JavaMail off iBiblio or something like that.
Comment 3 Yoav Shapira 2004-05-27 20:05:49 UTC
OK, I've done a build with these classes, tested it (works fine), and noted it 
to myself as part of the release management instructions.  I've also fixed 
build.properties.default to add a reference to the activation.jar.  
Comment 4 Renato 2004-06-21 22:23:14 UTC
I tested on tomcat 4.1.30 and it does not work either. 

I put the naming-factory.jar from 4.1.24 and everything worked again !
Comment 5 Yoav Shapira 2004-06-30 11:25:34 UTC
Then it's not a tomcat 5 bug, then.  I suggest you upgrade to tomcat 5.  I'm 
changing this issue to be for tomcat 4.
Comment 6 Mark Thomas 2004-11-15 21:52:13 UTC
This is fixed in 4.1.31