Issue

• Glassfish offered one benefit in its ease of managing connection pool/datasource relationship. Multiple JNDIs can be defined and all
  can tie back to a single connection pool definition.
  In JBoss it seems as if each connection pool must be unique to each JNDI.This makes configuration n times more redundant.
  Currently my thought is to refactor this application to have it not use so many JNDI datasource references . I would refactor the
  application to utilize the same jndi.
  The application as it stands now uses a separate JNDI reference for each project/component (Common, Util, EJB,Web, Core).
  Is there a way in JBoss EAP to have multiple XA Datasource JNDIs pointing to the same database connection pool ?- - - -