As EJB 3.1 tightened the screws on JNDI namespace format, wondering why there is a need for still maintaining JNDI specific configuration in the schema file. I mean, if the app server is going to do the bindings as per spec, is there a use case where specifying a user defined JNDI location in jboss.xml matters?
Oh, one more thing; while working on EJB 2.1 (wish if client is ready to move on to 3.1!) any JNDI names configured in jboss.xml are ignored. Though expected as per the spec, want to know if there is a way to enforce jboss.xml.