I’m wondering whether the Matterhorn architecture should push some of its cross-cutting concerns out to an ESB. Issues such as authentication, logging, auditing, etc could all be handled outside the container itself. This would imply that all service requests must be routed through the ESB.
In the OSGi context, clients would no longer connect directly to service implementations, even when they are deployed in the local container. They must always connect to service proxies, which route the service call out of the JVM, through the ESB, and back in through the service endpoint (REST or WSDL). The service proxy endpoints could be configured via the configuration admin service, or via context properties (e.g. config.properties).
The advantages include centralization of cross-cutting concerns, but all service requests would require marshalling/unmarshalling, or in other words would sacrifice runtime efficiency for centralized configuration / customization.