Java Client - OSGI module layer support

[glassfishrobot]

The OpenMQ jars (imq.jar, imqbroker.jar, etc.) are not bundles (they do not include OSGI metadata in their manifests).

It is therefore difficult to make use of the Java client code from within an OSGI project because of this, as the com.sun.messaging packages cannot be resolved by the OSGI framework (Apache Felix) at runtime.

The standard solution would be to "repackage" the jars as bundles, using the maven bundle plugin. Even this is difficult, however, as the jars are no longer available separately on maven central. Post 4.5.2, a zip (mq-distribution) is instead provided making it hard to declare dependencies on the particular projects your require.

The lack of OSGI metadata seems to be in contrast to the other Glassfish sub-projects (e.g shoal, grizzly), so it can come as a surprise to the unsuspecting developer.

Environment

Glassfish

Affected Versions

[current]

[glassfishrobot]

@glassfishrobot Commented
Reported by andrew_scully

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA MQ-328

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/openmq/issues/328
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @edbratt