[jboss-jira] [JBoss JIRA] (WFLY-2749) Unable to parse no-tx-separate-pools element of xa-pool in datasource definition

Tomaz Cerar (JIRA) issues at jboss.org
Mon Jan 13 10:17:33 EST 2014


     [ https://issues.jboss.org/browse/WFLY-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar updated WFLY-2749:
------------------------------

    Assignee: Stefano Maestri

    
> Unable to parse no-tx-separate-pools element of xa-pool in datasource definition
> --------------------------------------------------------------------------------
>
>                 Key: WFLY-2749
>                 URL: https://issues.jboss.org/browse/WFLY-2749
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA
>    Affects Versions: JBoss AS7 7.2.0.Final
>            Reporter: Kevin Formsma
>            Assignee: Stefano Maestri
>
> Defining a XA datasource with a pool as below fails. This element is valid in the schema documentation. The connector system fails to parse this, as in org.jboss.as.connector.subsystems.datasources.Constants.java the tag is mistyped as "no-tx-separate-pool" without the "pools".
> {code:xml}
>         <xa-pool>
>             <no-tx-separate-pools/>
>         </xa-pool>
> {code}
> Caused by: org.jboss.jca.common.metadata.ParserException: IJ010061: Unexpected element: no-tx-separate-pools
> 	at org.jboss.jca.common.metadata.ds.v11.DsParser.parseXaPool(DsParser.java:551)
> 	at org.jboss.jca.common.metadata.ds.v11.DsParser.parseXADataSource(DsParser.java:162)
> 	at org.jboss.jca.common.metadata.ds.v10.DsParser.parseDataSources(DsParser.java:185)
> 	at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:124)
> 	at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:87)
> 	at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:86)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list