Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365384 - Upgrade JavaMail to v1.4.4 or later
Summary: Upgrade JavaMail to v1.4.4 or later
Status: CLOSED DUPLICATE of bug 493611
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Glyn Normington CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-01 21:10 EST by Raman Gupta CLA
Modified: 2016-12-12 07:02 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Raman Gupta CLA 2011-12-01 21:10:08 EST 
Build Identifier: 

The ./repository/ext/javax.mail.glassfish_1.4.1.v201005082020.jar bundle is missing an import for javax.net.

When I tried to send a mail using JavaMail I got a ClassNotFoundException on javax.net.SocketFactory from the KernelBundleClassLoader for the javax.mail.glassfish bundle.

When I replaced javax.mail.glassfish with the mail-1.4.4 bundle from mvn:javax.mail.mail/1.4.4 then it worked fine.

Reproducible: Always

Steps to Reproduce:
1. Start Virgo
2. Try to send an e-mail from code.
3.
Comment 1 Glyn Normington CLA 2011-12-12 05:20:41 EST 
Is this running Virgo Tomcat Server or Virgo Jetty Server?
Comment 2 Raman Gupta CLA 2011-12-12 08:37:23 EST 
Virgo Jetty.
Comment 3 Glyn Normington CLA 2011-12-13 09:37:46 EST 
Raised http://java.net/jira/browse/GLASSFISH-17986 to get the missing import fixed.

Meanwhile, this problem can be worked around as described in the FAQ:

http://wiki.eclipse.org/Virgo/FAQ#How_can_I_import_a_package_into_someone_else.27s_bundle_without_hacking_the_manifest.3F
Comment 4 Glyn Normington CLA 2011-12-20 03:42:55 EST 
Re-opening to cover upgrading JavaMail since v1.4.4 contains the missing imports.
Comment 5 daniel marthaler CLA 2016-12-12 07:02:59 EST 

*** This bug has been marked as a duplicate of bug 493611 ***