There is one more issue connected to this:

when you create a datasource, there is xa-datasource-properties undefined, but when you try to enable the datasource, you get error, that you need to have at least one xa-datasource-property defined.

I think that defining this property shouldn't be required (I can fill it with any kind of data without any meaning to make enabling work, but it makes no sense putting it here just because of making possible to enable the datasource)

Steps to reproduce the issue with not defined xa-datasource-properties (the same goes for non XA datasource), the steps are for CLI:

1) start EAP 6 (6.1.0.DR4.1) in standalone mode
2) connect to it via CLI
3) create datasource: /subsystem=datasources/xa-data-source=testXA:add(xa-datasource-class=org.h2.jdbcx.JdbcDataSource, jndi-name=java:jboss/datasources/testXA,driver-name=h2)
4) run /subsystem=datasources/xa-data-source=testXA:read-resource and see that enabled is set to true and xa-datasource-properties is undefined
5) disabling the datasource: /subsystem=datasources/xa-data-source=testXA:disable (this is successful)
6) enable datasource: /subsystem=datasources/xa-data-source=testXA:enable (causes this error:
{
    "outcome" => "failed",
    "failure-description" => "JBAS010469: At least one xa-datasource-property is required for an xa-datasource",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}



Additional Info:

But if I add a property even though it is absolutely meaningless:
/subsystem=datasources/xa-data-source=testXA/xa-datasource-properties=someProp:add(value=someValue)
{
    "outcome" => "success",
    "response-headers" => {"process-state" => "reload-required"}
}

It suddenly works:
[standalone@localhost:9999 /] /subsystem=datasources/xa-data-source=testXA:enable
{
    "outcome" => "success",
    "response-headers" => {"process-state" => "reload-required"}
}
[standalone@localhost:9999 /]

(In reply to comment #1)

> I think that defining this property shouldn't be required (I can fill it
> with any kind of data without any meaning to make enabling work, but it
> makes no sense putting it here just because of making possible to enable the
> datasource)

You are wrong on this. For an xa-data-source at least one property is required because it's the only place where you can define connection parameters for xa-datasource. We can't check properties content because they are all database's vendor specific.

Ok, that makes sense. That clarifies my comment.

But the issue with enabled state set in default even though it cannot work (as the properties can be via CLI only added after the xa-datasource is created) remains

https://github.com/jbossas/jboss-eap/commit/d1d81750b8dfa4d576ec42d80e55ec75f946b268

Verified 6.1.0.ER3