geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2498) Geronimo should use the full javamail uber jar instead of just the spec jar + provider jar.
Date Wed, 25 Jul 2007 19:05:31 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick McGuire closed GERONIMO-2498.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Wish List)
                   2.0

> Geronimo should use the full javamail uber jar instead of just the spec jar + provider
jar.
> -------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2498
>                 URL: https://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
>            Assignee: Rick McGuire
>            Priority: Minor
>             Fix For: 2.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message