Relevant GH comment: https://github.com/openjdk/jmc/pull/548#issuecomment-1929038577

While working on pull/548 [0], @skarsaune has encountered an issue where the "org.openjdk.jmc.rjmx.jmxProtocols" extension point is not being handled in JMC 9.

This looks to be related to the rjmx code migration, and there is some more information in this GH comment: [1]. At first glance it looks like the ServiceFactoryInitializer will need to be updated to handle missing extension points, at the moment it only covers rjmx.service.

The reason for the Initializer class in the first place is that the extensions are Eclipse-specific and as-such are handled in jmc/application. Unfortunately this means that jmc/core cannot utilize the proper loading mechanism, so this Initializer class acts in the middle and loads the services from a given extension point and passes them into the connection handle (in core) via ServerHandle.

[0] https://github.com/openjdk/jmc/pull/548
[1] https://github.com/openjdk/jmc/pull/548#issuecomment-1930749297