Bug #82826 unneeded version requirement for javax.net.ssl Import-Package on OSGi MANIFES.MF
Submitted: 31 Aug 2016 16:34 Modified: 27 Oct 2016 15:24
Reporter: João Nelas Email Updates:
Status: In progress Impact on me:
Category:Connector / J Severity:S3 (Non-critical)
Version:5.1.36 OS:Any
Assigned to: Filipe Silva CPU Architecture:Any
Tags: OSGI

[31 Aug 2016 16:34] João Nelas
On the MANIFEST.MF file, the Import-Package directive specifies a version for the javax.net.ssl package:

Import-Package: javax.net, javax.net.ssl; version="[1.0.1, 2.0.0)"; resolution:=optional,...

Normally, javax packages are required without a version because they are exported by the system bundle with version 0.0.0 (they are a part of the jdk and so have no specific version)

When trying to use SSL to talk to a database, this leads to a failure to construct the connection because there is no javax.net.ssl package exported that respects the version range.

How to repeat:
In an OSGi environment try to configure an SSL connection to a mysql server.

Suggested fix:
Remove the version restriction.
[24 Oct 2016 15:28] Filipe Silva
Hi João,

Thank you for your interest in Connector/J.

This bug was verified against Apache Felix and it will be fixed as you  suggested.