You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Thilina Gunarathne (JIRA)" <ji...@apache.org> on 2008/12/18 14:31:44 UTC
[jira] Commented: (WSCOMMONS-417) Clarify the status of the
JavaMail dependency
[ https://issues.apache.org/jira/browse/WSCOMMONS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657768#action_12657768 ]
Thilina Gunarathne commented on WSCOMMONS-417:
----------------------------------------------
AFAIK Axis2 ships sun mail & activation implementations. A quick look at Axis2 1.4.1 confirmed this.
We got rid of the gerenimo-impl's when Sun changed mail & activation to a favorable license terms. I do not know about the current situation, but back then Gerenimo impl's were not complete. IIRC it was mostly the activation, where they did not support some content-type bindings.
+1 for switching completely to Sun mail+activation...
> Clarify the status of the JavaMail dependency
> ---------------------------------------------
>
> Key: WSCOMMONS-417
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-417
> Project: WS-Commons
> Issue Type: Improvement
> Components: AXIOM
> Reporter: Andreas Veithen
> Priority: Minor
> Fix For: Axiom 1.2.9
>
>
> axiom-api depends on Geronimo's JavaMail implementation. On the other hand, in axiom-tests this dependency is excluded and replaced by Sun's JavaMail dependency (same situation in Axis2).
> If Axiom doesn't work properly with Geronimo's JavaMail implementation, we should either make sure that the bugs in Geronimo get fixed or change the dependencies of axiom-api. If Axiom works properly with Geronimo's JavaMail implementation, then it doesn't make sense to run the tests against a different JavaMail implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.