[jira] Updated: (GERONIMO-2498) Geronimo should use the full javamail uber jar instead of just the spec jar + provider jar.
[ http://issues.apache.org/jira/browse/GERONIMO-2498?page=all ] Christopher M. Cardona updated GERONIMO-2498: - Affects Version/s: 2.0-M1 > Geronimo should use the full javamail uber jar instead of just the spec jar + > provider jar. > --- > > Key: GERONIMO-2498 > URL: http://issues.apache.org/jira/browse/GERONIMO-2498 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Affects Versions: 1.2, 2.0-M1 >Reporter: Rick McGuire > Assigned To: Rick McGuire >Priority: Minor > Fix For: Wish List > > > Unlike the Sun version of javamail, the Geronimo version is split into a spec > jar and a provider jar. This has caused numerous problems with users > attempting to use javamail from their applications. Many base components > have a javamail spec dependency, which causes the javamail api classes to be > loaded, but not the provider classes. The first hint of a problem is usually > a NoSuchProvider exception thrown when trying to create an smtp transport > instance. This generally takes some time to sort out. And even once the > dependency is added, there has been at least one occasion where it was > necessary to change the application to explicitly set the context classloader > before creating the Transport, thus requiring a change from an application > that worked on other servers. Again, this was caused by having spec and > provider jars managed by different classloader instances. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2498) Geronimo should use the full javamail uber jar instead of just the spec jar + provider jar.
[ http://issues.apache.org/jira/browse/GERONIMO-2498?page=all ] Rick McGuire updated GERONIMO-2498: --- Fix Version/s: Wish List (was: 1.2) > Geronimo should use the full javamail uber jar instead of just the spec jar + > provider jar. > --- > > Key: GERONIMO-2498 > URL: http://issues.apache.org/jira/browse/GERONIMO-2498 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Affects Versions: 1.2 >Reporter: Rick McGuire > Assigned To: Rick McGuire >Priority: Minor > Fix For: Wish List > > > Unlike the Sun version of javamail, the Geronimo version is split into a spec > jar and a provider jar. This has caused numerous problems with users > attempting to use javamail from their applications. Many base components > have a javamail spec dependency, which causes the javamail api classes to be > loaded, but not the provider classes. The first hint of a problem is usually > a NoSuchProvider exception thrown when trying to create an smtp transport > instance. This generally takes some time to sort out. And even once the > dependency is added, there has been at least one occasion where it was > necessary to change the application to explicitly set the context classloader > before creating the Transport, thus requiring a change from an application > that worked on other servers. Again, this was caused by having spec and > provider jars managed by different classloader instances. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
