Option for DataSources in JNDI to reflect changes to -ds.xml without being invalidated. --------------------------------------------------------------------------------------- Key: JBAS-5229 URL: http://jira.jboss.com/jira/browse/JBAS-5229 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Smiley I had to change my datasource in a -ds.xml file. When I did that, the DataSource that my web-app was using became invalid and so I needed to restart my application. It would be cool if there was an option for DataSources returned by JNDI to point to the latest real DataSource at that location so that the DataSource returned to the client isn't invalid. Perhaps you might do this internally like so: #1 used a wrapped DataSource for binding to JNDI. #2 When updating a -ds.xml, lookup the existing DataSource in JNDI, get the delegate, shut it down and add the new "real" DataSource. (in an atomic fashion -- naturally the DataSource needs to be synchronized). -- 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