[esb-issues] [JBoss JIRA] Commented: (JBESB-3582) SOA-P 5.1.0 classloader caching issues with embedded jar artifacts

[ https://issues.jboss.org/browse/JBESB-3582?page=com.atlassian.jira.plugin... ] Travis Rogers commented on JBESB-3582: -------------------------------------- SOA-P 5.0.2 shipped with the EsbWebServiceDeployer which handles the deployment of the HTTP listener servlet by attaching JBoss Web metadata to the deployment. In SOA-P 5.1, this functionality has been rolled into the main EsbDeployer, which eliminated the exceptional behavior experienced with HTTP listeners in 5.0.2. This link [1] offers further explanation why scoping your deployments may be necessary for your desired set up. The explanation for this is that by default all war deployments are treated as isolated deployments. The change mentioned in [1] modified this behavior and made the war deployments as non-isolated. The interesting part is that when there is a HTTP listener in the esb, the entire esb deployment is treated as a war and hence got isolated. Thanks to EsbWebServiceDeployer, the VFSDeploymentUnit is attached with JBossWebMetaData and hence the JBoss Deployer thinks it is a war. [1] http://community.jboss.org/wiki/useJBossWebClassLoaderinJBoss5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira