Revisit hibernate integration ----------------------------- Key: JBESB-2109 URL: https://jira.jboss.org/jira/browse/JBESB-2109 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner We need to revisit the hibernate integration and have another think about how this can be improved. The current implementation overwrites the hibernate session factory in JNDI without any checks to see whether it is safe to do so. Any active session at the JNDI location will be closed and a new one created using the gateway's configuration. This means that if the session factory had been previously setup by an application then we have no guarantee that we are duplicating the factory. Further complications arise when you consider that someone may want multiple listeners, doing different processing, on the same configuration. At present there is nothing to prevent the second instance from closing, then overwriting, the first. In addition, undeploying the listener will close the current factory leaving the application to cleanup, if indeed it can handle it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira