In LCDS 2.5 we had a major clean-up of the messaging component APIs to
prepare for publishing how to programmatically configure the message
broker. One change was to correct the APIs to reflect the in-memory
state of the components, such as how services, destinations and adapters
are actually managed. Services have a list of destinations, and each
destination creates its own instance of an adapter.If you want to get to
a service from a custom adapter, you can either do what you mention
below and...