Binder services should not be ON_DEMAND

IF a binder service is registered as ON_DEMAND then the item will not be available for lookup in JNDI until something as expressed a dependency on it. This means that it will work for resource injection, however will fail for manual JNDI lookups.

If lazy startup is required the binder service should use a ManagedReferenceFactory that starts the lazy service and blocks until the lazy service is available.