[ARTEMIS-1252] Add service loading of password codec to obtain its implementation from the application’s root context, rather than using a class loader

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.5, 2.1.0
• Fix Version/s: 2.2.0
• Assignee: Unassigned
• Reporter: Armand Roelens
• Created: 26/Jun/17 15:03
• Updated: 25/Jul/17 16:15
• Resolved: 25/Jul/17 16:15

Description

The current implementation for retrieving a custom password codec forces every OSGI bundle requiring the password codec (which can be every bundle with its own client that attempts to connect to the broker) to import the package containing the custom password codec.

If the password codec is instead service loaded, none of the OSGI bundles need to import the package containing the password codec. That password codec package does need to advertise its implementation via a configuration file, but that change is limited to just that package.

Add service loading of the custom password codec, and as a fallback, if no service is found, maintain the current implementation of using normal class loading.

Issue Links

• links to: GitHub Pull Request #1366