[
https://issues.jboss.org/browse/CDI-409?page=com.atlassian.jira.plugin.sy...
]
Bruno Borges commented on CDI-409:
----------------------------------
Antonio, how would the underlying runtime environment know which DataSource to load? And
why would only one alternative be enough? Certainly, developers will want to have more
options (integration, qa, pre-production).
Having @Alternatives for resource definition
--------------------------------------------
Key: CDI-409
URL:
https://issues.jboss.org/browse/CDI-409
Project: CDI Specification Issues
Issue Type: Bug
Affects Versions: TBD
Reporter: Antonio Goncalves
Java EE 6 introduced @DataSourceDefinition and Java EE 7 introduced the same way of
defining other resources (JMS factory/destination, Mail factory, JCA connectors....).
It would be interesting to have @Alternatives working with these resource definitions.
For example you could have a default DS for development :
{code}
@DataSourceDefinition(
className = "org.apache.derby.jdbc.EmbeddedDataSource",
name = "java:global/jdbc/devDS",
user = "dev",
password = "dev",
databaseName = "dev",
properties = {"connectionAttributes=;create=true"}
)
public class DevResources {...}
{code}
And another DS that would be used, let say, in production as an alternative :
{code}
@Alternative
@DataSourceDefinition(
className = "org.apache.derby.jdbc.EmbeddedDataSource",
name = "java:global/jdbc/prodDS",
user = "prod",
password = "prod",
databaseName = "prod",
properties = {"connectionAttributes=;create=true"}
)
public class ProdResources {...}
{code}
--
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