SOA-P 5.1.0 classloader caching issues with embedded jar artifacts
------------------------------------------------------------------
Key: JBESB-3582
URL:
https://issues.jboss.org/browse/JBESB-3582
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 5.0 Milestone Release 1
Environment: Windows 7
Reporter: Dave Siracusa
An existing .ESB file with embedded jar artifact ends up being used for subsequently
deployed .ESB applications even if the second ESB contains a newer/different version of
the embedded jar artifact.
If you repeatly redeploy the first and the second, eventually the ESB file fails to deploy
due to duplicate class issues.
SOA-P 5.0.0/1/2 does not behave this way as the VFSClassloader uniquely captures each
artifact in the tmp vsf folder.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira