[thomas.diesler]

So here's a potentially controversial idea: how about we only enable  servicemix with non-osgi deployments that actually have their exports  and imports defined as such. Otherwise they dont get to play in  servicemix. Adding a few headers is only a small task and making it a  requirement provides yet another reason for people to properly declare  this information.

This is unlikely to work because we don't control all deployments that go into JBossAS. Although we might be able to migrate service jboss-foo into osgi land by providing ogsi metadata. We would at the same time break service acme-bar, which has a dependency on jboss-foo.

The wiring between osgi and non-osgi deployments needs to be done at the lowest common denominator, which is the MC. When all those non-osgi deployments enter the scene and expose their capabilities to osgi bundles we need to make sure that we do not have unintended leakage.