[
http://jira.jboss.com/jira/browse/JBSEAM-1410?page=all ]
Alex Savitsky updated JBSEAM-1410:
----------------------------------
Attachment: TomcatDataSourceFactory.java
My first stab at resolving this issue. The attached code looks up the DataSource in Tomcat
JNDI (hardcoded, could be externalized into a property), then binds it to MC JNDI the same
way as LocalTxDataSource.start() does it.
Make Microcontainer to use Tomcat-defined datasources
-----------------------------------------------------
Key: JBSEAM-1410
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1410
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Alex Savitsky
Attachments: TomcatDataSourceFactory.java
Currently, when deploying on Tomcat+Microcontainer stack, the only way to define a
DataSource is to define it in jboss-beans.xml file, which is located INSIDE the deployed
WAR.
A common (and de-facto standard) requirement for production deployments is to let server
admin to define the data source, so as not to expose production DB credentials to
developers. This requires for the data source definition to be outside of the deployed
WAR, either in Tomcat's server.xml file, or in META-INF/context.xml. It would be nice
if there would be a way to use that external datasource, instead of defining it in
jboss-beans.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira