search

javaee / ejb-spec

See javax.ejb project for API. Contains legacy issues only.
https://github.com/javaee/javax.ejb
6 stars 1 forks source link

Remote JNDI naming convention isn't clear enough #105

Open glassfishrobot opened 11 years ago

glassfishrobot commented 11 years ago

Based on this thread:

http://java.net/projects/ejb-spec/lists/users/archive/2012-11/message/17

It seems as though vendors are still not clear that Remote JNDI names should not be any different from Local JNDI names. Based on some initial feedback from the EG, it seems as though the EG believes it is clear enough in the spec. I would like to request that the EJB EG provide further clarity, or that members representing organizations that don't believe the standard JNDI names apply to remote (Apache, JBoss/RedHat) clarify why they believe as such.

glassfishrobot commented 11 years ago

Reported by genomeprjct

glassfishrobot commented 11 years ago

genomeprjct said: Title should be "Remote JNDI naming convention isn't clear enough."

glassfishrobot commented 11 years ago

mvatkina said: fixed

glassfishrobot commented 11 years ago

Was assigned to mvatkina

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA EJB_SPEC-105