Rick
There have been 3 javamail questions on the user list in recent weeks
about how to resolve a NoSuchProviderException trying to use SMTP.
These problems all had the same root cause, having the javax.mail and
the provider implementations in separate jar files. It's not obvious to
most people that the dependency requirement exists and occasionally,
even adding the dependency doesn't fix the problem. There was a recent
problem of trying to use javamail from a Quartz job class where it was
necessary to explicitly set the context classloader before requesting a
transport instance to ensure the correct class loader was getting used.
This was a situation that could not occur with the Sun javamail
implementation because the api code and the providers are contained in
the same jar file.
This problem can be easily corrected if we just switched the references
to the javamail spec file to the geronimo-javamail_1.3_mail uber jar
that contains the merged spec and provider classes. More and more users
are tripping over this problem, which can be very easily corrected. Are
there any objections to making this change in 1.2?
- Fixing javamail (again) Rick McGuire
- Re: Fixing javamail (again) Jay D. McHugh
- Re: Fixing javamail (again) Rick McGuire
