JNDI simplification and enhancements

[glassfishrobot]

Dear EG,
after reading this and trying to create services and expose them through JNDI, I have come up with an idea to simplify and standardize the way currently we can bind/unbind services on a JNDI. The Wildfly team has this reference material that the implement on top of the standard of JavaEE spec
https://docs.jboss.org/author/display/WFLY8/JNDI+Reference.
My ideas came from the fact that I want to have some services exposed but I don't want them to be either EJB's, I don't need all the EJB world since I don't have transactions etc and on top of that I want them to be remote accessible. Currently this can be achieved by some vendor specific configuration or configuration on the web.xml of your webapp. But why not enable an annotation something like @jndi or portable CDI things where you can define lightweight JNDI look able services. I firmly believe that this will help improving the adoption of Java EE since the accusation for heavy weight components will no longer stands true from any point of view.

[glassfishrobot]

Reported by nmpallas

[glassfishrobot]

@bshannon said:
Only a few Java EE component types are remotely accessible, and certainly not all CDI beans are.

Other than EJBs, the remotely accessible components are web services, JAX-RS endpoints, and Servlets in general. There is a JNDI name for the URL corresponding to a web application context root, from which you can derive the URL for any of the endpoints within the web application; see section 15.2.3 of the Servlet spec.

What kind of services do you want to expose using what remote access protocol?

[glassfishrobot]

This issue was imported from java.net JIRA JAVAEE_SPEC-40