Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:

Suppose you have a jdbc driver module: 'oracle.jdbc' with slot: '11.1'

Steps to Reproduce:
1. Start EAP 6.4 in domain mode: bin/domain.sh
2. Start EAP 6 CLI console: bin/jboss-cli.sh -c
3. Run:

/profile=full/subsystem=datasources/jdbc-driver=oracle11.1:add(driver-name=oracle11.1,driver-module-name=oracle.jdbc,driver-xa-datasource-class-name=oracle.jdbc.xa.client.OracleXADataSource,module-slot=11.1)

Actual results:
 <driver name="oracle11.1" module="oracle.jdbc">
      <xa-datasource-class>
         oracle.jdbc.xa.client.OracleXADataSource
      </xa-datasource-class>
 </driver>

 is persisted in domain.xml

Expected results:
 <driver name="oracle11.1" module="oracle.jdbc:11.1">
      <xa-datasource-class>
         oracle.jdbc.xa.client.OracleXADataSource
      </xa-datasource-class>
 </driver>

 is persisted in domain.xml

Additional info:

  The inconsistent persistence will lead to wrong module:slot used after server restarted.