The resource adapter implementations should NOT depend upon the connection manager
implementation or transaction manager or any other jboss service.

This is the wrong way around. It is like coding an EJB to use specifics of a JBoss EJB container.

Related, each resource adapter should be useable in a standalone environment
(with an internal dummy connection manager) through the alternate api

See javax.resource.spi.ManagedConnectionFactory

/**

• Creates a connection factory instance. The connection manager is provided
• by the resource adapter.
  *
• STANDALONE USE
  *
• @return the connection factory
• @throws ResourceException for a generic error
• @throws ResourceAdapterInternalException for an internal error in the
• resource adapter
  */
  public Object createConnectionFactory() throws ResourceException;

/**

• Creates a connection factory instance. the connection manager is provided
• by the application server
  *
• APPLICATION SERVER/EXTERNAL CONNECTION MANAGER USE
• @param cxManager the connection manager
• @return the connection factory
• @throws ResourceException for a generic error
• @throws ResourceAdapterInternalException for an internal error in the
• resource adapter
  */
  public Object createConnectionFactory(ConnectionManager cxManager) throws ResourceException;