Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <2025288899.1139584677388.JavaMail.jira@ajax.apache.org>
Date: Fri, 10 Feb 2006 16:17:57 +0100 (CET)
From: "Rick McGuire (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-1619) Using Geronimo version of javamail
 with AXIS2 uncovers multiple errors.
In-Reply-To: <1940535083.1139584558413.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-1619?page=all ]

Rick McGuire updated GERONIMO-1619:
-----------------------------------

    Attachment: GERONIMO-1619-javamail.patch

Patch to the geronimo-spec-javamail module. 

> Using Geronimo version of javamail with AXIS2 uncovers multiple errors.
> -----------------------------------------------------------------------
>
>          Key: GERONIMO-1619
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1619
>      Project: Geronimo
>         Type: Bug
>   Components: mail, specs
>     Versions: 1.1
>     Reporter: Rick McGuire
>  Attachments: GERONIMO-1619-activation.patch, GERONIMO-1619-javamail.patch
>
> Attempting to run the AXIS tests against the Geronimo javamail code uncovered multiple problems.  Among the problems uncovered were:
> - No JAF handlers for MimeMultipart objects (or Html and Message, which the Sun version also supports). 
> - No processing of x-java-fallback-entry parameters on mailcap file records. 
> - No support for fallback handlers in handler resolution. 
> - Incorrect serialization of ContentType/Parameter list objects.
> - Incorrect processing of MIME identifiers when resolving content-handlers. 
> These patches correct these problems, but there is another problem with the build (GERONIMO-1618) that will prevent these fixes from becoming fully operational. 

-- 
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