[
https://issues.apache.org/jira/browse/CLEREZZA-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169363#comment-13169363
]
Florent ANDRE commented on CLEREZZA-656:
----------------------------------------
As I read, javax.activation in j2se is the same as the one in the bundle.
Two bundles exporting the same lib at different version number could normally
no cause problems in OSGI.
The point is : in order to correctly handle incoming mail / multipart things,
javax.activation and javax.mail need to share the same classloader. If not,
javax.activation don't detect the correct class type.
++
> Correct handling of javax.mail and javax.activation in OSGI environnement
> -------------------------------------------------------------------------
>
> Key: CLEREZZA-656
> URL: https://issues.apache.org/jira/browse/CLEREZZA-656
> Project: Clerezza
> Issue Type: Bug
> Reporter: Florent ANDRE
> Labels: ext-javax-mail
> Fix For: 0.2-incubating
>
> Attachments: export-activation-for-datahandler.patch,
> ext-javax-mail-osgi.patch
>
>
> In OSGI environnement, mail sending [1] or parsing [2] don't work well.
> This problems are due to Classloader issue in javax.activation (that try to
> get resources in javax.mail with ClassLoader.getRessource ([3])
> [1] : http://thecarlhall.wordpress.com/2009/10/27/javamail-in-osgi/
> [2] : http://old.nabble.com/JavaMail-and-Felix-td32000484.html,
> http://nostacktrace.com/dev/2010/6/24/sending-multipart-mail-in-an-osgi-container.html
> [3] :
> http://kenai.com/projects/javamail/forums/forum/topics/13123-multipart-alternative#p27947
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
