You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2012/10/08 07:14:03 UTC

[jira] [Reopened] (OPENEJB-1665) @DataSourceDefinition support

     [ https://issues.apache.org/jira/browse/OPENEJB-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins reopened OPENEJB-1665:
------------------------------------

    
> @DataSourceDefinition support
> -----------------------------
>
>                 Key: OPENEJB-1665
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1665
>             Project: OpenEJB
>          Issue Type: New Feature
>          Components: configuration, deployment
>            Reporter: David Blevins
>             Fix For: 4.0-beta-1, 4.5.0
>
>
> Had thought there was a JIRA for this already.  Guess not.  Anyway, the changes:
>  - Support for deployment descriptor declared <data-source> elements
>  - @DataSourceDefinition annotations are translated into the equivalent JAXB object (not directly into a Resource object)
>  - JAXB DataSource definitions are translated into Resource objects prior to AutoConfig
>  - DataSources created from definitions are prefixed with the appName prior to binding into the private openejb/Resource/ namespace
>  - A single JNDI reference hardcoded to point to the DataSource definition will automatically created and added to all the consumers.
>  - Raw version of the DataSource definition properties are passed straight through to the DataSourceFactory so that it may use them to internally construct the DataSource via xbean-reflect
>  - Respect xml overriding -- ignore the annotation data if the DataSource is defined in xml

--
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