Creating XA datasource requires driver name and version ------------------------------------------------------- Key: AS7-723 URL: https://issues.jboss.org/browse/AS7-723 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 It's weird, because the XA datasource itself just relies on the DataSource class. The driver and version info is only needed to identify the module/service: Request { "operation" => "add", "address" => [ ("profile" => "default"), ("subsystem" => "datasources"), ("xa-data-source" => "H2XADS") ], "name" => "H2XADS", "jndi-name" => "H2XADS", "enabled" => true, "xa-data-source-class" => "org.h2.jdbcx.JdbcDataSource", "pool-name" => "H2XADS_Pool", "user-name" => "sa", "password" => "sa", "xa-data-source-properties" => [("URL" => "jdbc:h2:mem:test")], "child-type" => undefined } Response Internal Server Error { "outcome" => "failed", "result" => {"server-groups" => {"main-server-group" => { "server-two" => { "host" => "local", "response" => { "outcome" => "failed", "failure-description" => "java.util.NoSuchElementException: No child 'driver' exists" } }, "server-one" => { "host" => "local", "response" => { "outcome" => "failed", "failure-description" => "java.util.NoSuchElementException: No child 'driver' exists" } } }}}, "failure-description" => "Operation was not applied successfully to any servers" } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira