[
https://issues.apache.org/jira/browse/JAMES-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439051#comment-13439051
]
Idea Harness edited comment on JAMES-1433 at 8/22/12 8:34 AM:
--------------------------------------------------------------
Eric,
I am actually seeing the reverse ie. Oracle JavaMail sets the ContentType
header correctly to "text/html" (from the default of "text/plain") in the
MimeBodyPart.setText(String text, String charset, String subtype) method call,
whereas Geronimo JavaMail does not. This breaks one of my unit tests. Here is
the code
// By default has ContentType="text/plain"
MimeBodyPart bodyPart = new MimeBodyPart();
bodyPart.setText( "<html><head></head><body><div>Here we
go</div></body></html>", "US-ASCII" /* charset */, "html" /* subType */ );
After the above code :
a. If executed with only Oracle JavaMail (ie. if only mail-1.4.4.jar is in
JAMES/conf/wrapper.conf) then bodyPart.getContentType() CORRECTLY startsWith()
"text/html"
b. If executed with only Geronimo JavaMail (ie. if only
geronimo-javamail_1.4_mail-1.8.3.jar is in JAMES/conf/wrapper.conf) then
bodyPart.getContentType() INCORRECTLY startsWith() "text/plain".
Also I am curious which james-server-core tests were breaking and which you
fixed after you switched to only use geronimo-javamail_1.4_mail-1.8.3.jar.
Maybe, it's a bit premature to switch to geronimo-javamail_1.4_mail-1.8.3.jar
just yet ? I'd hate to code / work around vendor specific implementations. Just
my 2c.
Regards,
IH
was (Author: idea.harness):
Eric,
I am actually seeing the reverse ie. Oracle JavaMail sets the ContentType
header correctly to "text/html" (from the default of "text/plain") in the
MimeBodyPart.setText(String text, String charset, String subtype) method call,
whereas Geronimo JavaMail does not. This breaks one of my unit tests. Here is
the code
// By default has ContentType="text/plain"
MimeBodyPart bodyPart = new MimeBodyPart();
bodyPart.setText( "<html><head></head><body><div>Here we
go</div></body></html>", "US-ASCII" /* charset */, "html" /* subType */ );
After the above code :
a. If executed with only Oracle JavaMail (ie. if only mail-1.4.4.jar is in
JAMES/conf/wrapper.conf) then bodyPart.getContent() CORRECTLY startsWith()
"text/html"
b. If executed with only Geronimo JavaMail (ie. if only
geronimo-javamail_1.4_mail-1.8.3.jar is in JAMES/conf/wrapper.conf) then
bodyPart.getContent() INCORRECTLY startsWith() "text/plain".
Also I am curious which james-server-core tests were breaking and which you
fixed after you switched to only use geronimo-javamail_1.4_mail-1.8.3.jar.
Maybe, it's a bit premature to switch to geronimo-javamail_1.4_mail-1.8.3.jar
just yet ? I'd hate to code / work around vendor specific implementations. Just
my 2c.
Regards,
IH
> Upgrade to geronimo-javamail_1.4 1.8.3 and exclude oracle mail
> --------------------------------------------------------------
>
> Key: JAMES-1433
> URL: https://issues.apache.org/jira/browse/JAMES-1433
> Project: JAMES Server
> Issue Type: Bug
> Affects Versions: 3.0-beta5
> Reporter: Eric Charles
> Assignee: Eric Charles
> Priority: Minor
> Fix For: 3.0-beta5
>
>
> See JAMES-1431
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
