users@glassfish.java.net

RE: Issues with JavaMail in OSGi Bundle

From: Martin Gainty <mgainty_at_hotmail.com>
Date: Wed, 4 Aug 2010 13:50:19 -0400

Robert
 
take a look at
http://forums.sun.com/thread.jspa?threadID=5353050

hth
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.



 

> From: RWeeks_at_ext-inc.com
> To: users_at_glassfish.dev.java.net
> Date: Wed, 4 Aug 2010 10:25:51 -0700
> Subject: Issues with JavaMail in OSGi Bundle
>
> Hello -
>
> We are seeing an issue we can't seem to get past when creating multipart mail messages within an OSGi bundle using JavaMail (the included module in Glassfish) - using v3.0.1.
>
> I have searched and have seen this issue, and it was said to be fixed, but we are seeing it quite readily.
>
> The error we are getting is:
>
> javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/alternative;
>
> I know this was caused by the JAF looking for the mailcap file within the META-INF directory - and there were some classloading issues that were present - but this was supposedly fixed in 3.0.
>
> If I look at the properties manually before I do any of the calls, I can see them there:
>
> MailcapCommandMap mc = (MailcapCommandMap) CommandMap.getDefaultCommandMap();
> for (String type: mc.getMimeTypes()) {
> log.debug(" Type ): " + type);
> }
>
>
> as well as I have tried to set them this way - but to no avail. We consistently get this message when trying set the content.
>
> Is anyone else still seeing this as well - and if so, how to get around it?
>
> I have tried quite a few routes and wanted to get anyone else's experiences with this.
>
> Thanks a lot.
>
> --
> Robert B. Weeks
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>