[jboss-jira] [JBoss JIRA] Resolved: (JBMETA-318) EJB3.1 MetaData needs to account for data-source(s).

[Weston M. Price (JIRA)]

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

Weston M. Price resolved JBMETA-318.
------------------------------------

    Fix Version/s: 2.0.0.CR1
       Resolution: Done


Added @DataSourceDefinition support for EJB based components and modules.

> EJB3.1 MetaData needs to account for data-source(s).
> ----------------------------------------------------
>
>                 Key: JBMETA-318
>                 URL: https://issues.jboss.org/browse/JBMETA-318
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ejb
>    Affects Versions: jboss-metadata-ejb-2.0.0-alpha-25
>         Environment: All platforms.
>            Reporter: Weston M. Price
>            Assignee: Weston M. Price
>             Fix For: 2.0.0.CR1
>
>
> In EJB3.1, data-source(s) can be defined in the ejb-jar.xml file as well as using the @DataSourceDefinition on ejb components. In the ejb-jar.xml file, the data-source element appears as part of the jndiEnvironmentRefsGroup and can be deployed for individual EJB components. Similarly, the @DataSourceDefinition(s) annotation can appear on each EJB type. Currently, the EJB metadata does not parse or create this portion of metadata. This needs to be added to support the EE6 specification part EE5.17 and exposed to clients that need this information to deploy the data source (ie, the new DataSourceDeployer as part of the connector project.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira