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 "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/12/18 14:21:44 UTC
[jira] Created: (WSCOMMONS-417) Clarify the status of the JavaMail
dependency
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.
[jira] Resolved: (WSCOMMONS-417) Clarify the status of the JavaMail
dependency
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved WSCOMMONS-417.
---------------------------------------
Resolution: Fixed
Axiom (including the tests) now works correctly with the Geronimo JARs. Therefore I'm going to close this issue. Note that Axis2 still overrides the dependency to use Sun's implementations.
> 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.
[jira] Commented: (WSCOMMONS-417) Clarify the status of the
JavaMail dependency
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761849#action_12761849 ]
Andreas Veithen commented on WSCOMMONS-417:
-------------------------------------------
On a similar question in the context of CXF, Daniel Kulp gave some additional arguments in support of the Geronimo implementations. See [1].
[1] http://markmail.org/message/xanxtu2s4ukjhn3k
> 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.
[jira] Commented: (WSCOMMONS-417) Clarify the status of the
JavaMail dependency
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657803#action_12657803 ]
Andreas Veithen commented on WSCOMMONS-417:
-------------------------------------------
Jarek,
I still have two open issues with Geronimo JavaMail: GERONIMO-4352 and GERONIMO-4421. The first one causes failures in the mail transport (if we move to Geronimo, we should make sure that the mail transport works reasonably well with it) and the second will potentially cause an issue for Axiom itself. Maybe you can push a bit so that they get solved?
> 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.
[jira] Commented: (WSCOMMONS-417) Clarify the status of the
JavaMail dependency
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (WSCOMMONS-417) Clarify the status of the
JavaMail dependency
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657796#action_12657796 ]
Jarek Gawor commented on WSCOMMONS-417:
---------------------------------------
(As a Geronimo person) I think it would be good to use Geronimo jars over Sun. The Geronimo JavaMail implementation is much better now and we are pretty good about fixing bugs in it.
> 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.
Re: [jira] Commented: (WSCOMMONS-417) Clarify the status of the JavaMail
dependency
Posted by "Asankha C. Perera" <as...@apache.org>.
Andreas
Do you know if its safe to exclude Geronimo JARs from Axiom-api .. its
becoming a transitive dependency?
thanks
asankha
[jira] Commented: (WSCOMMONS-417) Clarify the status of the
JavaMail dependency
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689452#action_12689452 ]
Asankha C. Perera commented on WSCOMMONS-417:
---------------------------------------------
I think the problem occurred since earlier versions of Sun Javamail or Activation were not available on M2 repos probably due to some licensing issues.
Now Axis2 poms have a dependency on both Geronimo and Sun Javamail, which creates problems [1], and confusion
I would like the Axis2 mail transport to depend on Sun Javamail v1.4.2 (which is the latest as of now and available on M2 Repos), and exclude the use of geronimo JARs altogether for the Commons Transports 1.0 release
[1] http://forums.sun.com/thread.jspa?messageID=10657165
> 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.