The error which you mentioned like [WFLYNAM0043: Naming context is read-only]   you will get if you will try to bind custom objects to read only contexts

like  "java:module" or "java:module", "java:comp" ......etc"

InitialContext ic = new InitialContext(); 

aaa.bbb.Test  test = new aaa.bbb.Test(); 

ic.rebind("java:app/SomeProcess",test);     // WRONG 

//  OR 

ic.rebind("java:module/SomeProcess",test);        // WRONG 

//  OR 

ic.rebind("java:comp/SomeProcess",test);     // WRONG         

Are there any jndi.properties files in any of your applications, if so, they should be removed

Are there any system properties set such as -Djava.naming.provider.url

Make sure new InitialContext() is used and no properties are being passed in.

Section EE.5.3.4 of the Java EE spec says:

The container must ensure that the application component instances have only

read access to their naming context. The container must throw the

javax.naming.OperationNotSupportedException from all the methods of the

javax.naming.Context interface that modify the environment naming context and

its subcontexts.

It seems pretty natural and handy to allow one application publish something to the JNDI at runtime and let other application to access it.

The easiest way to bind those objects would be to use a @javax.ejb.Startup @javax.ejb.Singleton and bind them in @PostConstruct method. You won't have to do anything additional and you won't even need the sar (assuming that's the only thing you are using it for):

~~~

@Singleton 

@Startup 

public class SomeServiceManager { 

@PostConstruct 

private void onConstruct() { 

Context context = new InitialContext(); 

     try { 

          context.bind(SERVICE_NAME, this); // where SERVICE_NAME is "java:/SomeServiceManager" or similar 

     } catch(NamingException e ) { 

          logger.error("Failed to bind name in context", e); 

     } 

...  

} 

} 

~~~

Is that something that you want to try?