JBossDeveloper

For subsystem related bindings which have no deployments involved, JNDI API is not used, example:

{code:java}

@Override

    protected void performRuntime(OperationContext context, ModelNode operation, ModelNode model, ServiceVerificationHandler verificationHandler, List<ServiceController<?>> newControllers) throws OperationFailedException {

        // creates binder service

        final String bindValue = new Object();      

        final ContextNames.BindInfo bindInfo = ContextNames.bindInfoFor("java:jboss/BPELEngine");

        final BinderService binderService = new BinderService(bindInfo.getBindName());

        binderService.getManagedObjectInjector().inject(new ValueManagedReferenceFactory(new ImmediateValue<Object>(bindValue)));

        // creates the service builder with dep to the parent jndi context

        ServiceBuilder<ManagedReferenceFactory> builder = context.getServiceTarget().addService(bindInfo.getBinderServiceName(), binderService)

                .addDependency(bindInfo.getParentContextServiceName(), ServiceBasedNamingStore.class, binderService.getNamingStoreInjector());

        // installs the service

        newControllers.add(builder.install());

    }

{code}

That means Jaikiran suspicions were correct, there is no deployment involved, when that happens there is no JndiNamingDependencyProcessor available, so there is no solution using JNDI API, you must go for the non JNDI API solution in my post above, slighty changed to something like this:

public void bind(String name, Object value) throws NamingException {
        try {
            ServiceContainer serviceContainer = CurrentServiceContainer.getServiceContainer();
            // creates binder service
            final ContextNames.BindInfo bindInfo = ContextNames.bindInfoFor(name);
            final BinderService binderService = new BinderService(bindInfo.getBindName());
            binderService.getManagedObjectInjector().inject(new ValueManagedReferenceFactory(new ImmediateValue<Object>(value)));
            // creates the service builder with dep to the parent jndi context
            ServiceController<?> serviceController = serviceContainer.addService(bindInfo.getBinderServiceName(), binderService)
              .addDependency(bindInfo.getParentContextServiceName(), ServiceBasedNamingStore.class, binderService.getNamingStoreInjector())
              .setInitialMode(ServiceController.Mode.ACTIVE)
              .install();
            // wait for the service start
            final StabilityMonitor monitor = new StabilityMonitor();
            monitor.addController(serviceController);
            try {
                monitor.awaitStability();
            } finally {
                monitor.removeController(serviceController);
            }
            final Exception startException = serviceController.getStartException();
            if (startException != null) {
                throw startException;
            }
        } catch (NamingException e) {
            throw e;
        } catch (Throwable e) {
            final NamingException ne = new NamingException("Failed to bind "+ value + " at location " + name);
            ne.setRootCause(e);
            throw ne;
        }        
    }
    
    public void unbind(String name) throws NamingException {
        try {
            ServiceContainer serviceContainer = CurrentServiceContainer.getServiceContainer();
            final ContextNames.BindInfo bindInfo = ContextNames.bindInfoFor(name);
            final ServiceController<?> serviceController = serviceContainer.getService(bindInfo.getBinderServiceName());
            if (serviceController == null) {
                throw new NameNotFoundException(name);
            }
            serviceController.setMode(ServiceController.Mode.REMOVE);
            final StabilityMonitor monitor = new StabilityMonitor();
            monitor.addController(serviceController);
            try {
                monitor.awaitStability();
            } finally {
                monitor.removeController(serviceController);
            }
        } catch (NamingException e) {
            throw e;
        } catch (Throwable e) {
            final NamingException ne = new NamingException("Failed to unbind " + name);
            ne.setRootCause(e);
            throw ne;
        }           
    }

Note that I did not test this code, I simply adapted WritableServiceBasedNamingStore's bind and unbind logic to your case. Also it would be better for you to use the Shipward's service target instead of the current service container. Please let me know if anything fails.

Now, looking at this particular use case, and the solution, I agree a simple API that do not requires working out with MSC is needed for subsystem/modules. Some options:

1) Allow the deployment service name to not be set through WritableServiceBasedNamingStore.pushOwner(), i.e. WritableServiceBasedNamingStorethis's bind() and unbind() would understand that if owner not set the op is related to a non managed bind. Like I said earlier, this could open the door for bugs based on developer forgetting to use pushOwner() when they should. A good thing of this solution is that code depends only on JNDI, and no particular properties need to be set, which means code could be easily ported to another container. No chance of defining a specific service target.

2) Provide an alternative JNDI context impl, available by passing config properties on new InitialContext(properties). No doors open for misusage, dependency only on JNDI api, but probably not portable code.  No chance of defining a specific service target.

3) Provide a specific API that restores the missed functionality, something like WritableServiceBasedNamingStore.unmanagedBind(String name, Object value, ServiceTarget serviceTarget) and WritableServiceBasedNamingStore.unmanagedUnbind(String name, ServiceTarget serviceTarget). A solution that clearly defines the functionality with hard chance of misusage, which allows a specific service target to be used, but there is dependency on AS Naming.

From the AS Naming dev point of view I'm more into 3) anyway... Thoughts?