[
https://issues.jboss.org/browse/WFLY-7726?page=com.atlassian.jira.plugin....
]
Guillermo González de Agüero updated WFLY-7726:
-----------------------------------------------
Description:
When a Datasource is defined either using @DatasourceDefinition or via web.xml, it
isn't registered in the deployment model at /deployment=xx.war/subsystem=datasources.
It works as expected when deploying the datasource via the deprecated *-ds.xml way.
Looking at the code, it seems that DataSourceDefinitionAnnotationProcessor and
DataSourceDefinitionDescriptorProcessor just need to add the resource to the
org.jboss.as.server.deployment.Attachments.DEPLOYMENT_RESOURCE_SUPPORT as
DsXmlDeploymentInstallProcessor does.
was:
When a Datasource is defined either using @DatasourceDefinition or via web.xml, it
isn't registered in the deployment model at /deployment=xx.war/subsystem=datasources.
It works as expected when deploying the datasource via the deprecated *-ds.xml way.
Expose @DataSourceDefiniton connections in the deployment model
---------------------------------------------------------------
Key: WFLY-7726
URL:
https://issues.jboss.org/browse/WFLY-7726
Project: WildFly
Issue Type: Enhancement
Components: JCA
Affects Versions: 10.1.0.Final
Reporter: Guillermo González de Agüero
Assignee: Stefano Maestri
When a Datasource is defined either using @DatasourceDefinition or via web.xml, it
isn't registered in the deployment model at /deployment=xx.war/subsystem=datasources.
It works as expected when deploying the datasource via the deprecated *-ds.xml way.
Looking at the code, it seems that DataSourceDefinitionAnnotationProcessor and
DataSourceDefinitionDescriptorProcessor just need to add the resource to the
org.jboss.as.server.deployment.Attachments.DEPLOYMENT_RESOURCE_SUPPORT as
DsXmlDeploymentInstallProcessor does.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)