Hide Forgot
Date of First Response: 2007-10-11 07:52:34 project_key: SOA Aleksandar Kostadinov commented on JBQA-1095: --------------------------------------------- We should also ensure all jars with the same name in the distribution are the same. Example from current version: cdf1d84e1e6d0e3a3354e82473a48c23 ./server/default/deploy/jbpm.esb/hibernate3.jar 6e02a434257e35ef95024ab0d22d802c ./server/default/lib/hibernate3.jar 0b9e342ecfed2af5d020f9bc92f61d3a ./tools/console/management-web/lib/hibernate3.jar As well in ESB I've seen ./server/default/deploy/jbpm.esb/hibernate3.jar as well ./server/default/deploy/hibernate3.jar so we have t check for such situations as well.
the non standalone version has 3 different version of hibernate, several with different checksums see atched file
Attachment: Added: xx
Link: Added: This issue is related to JBESB-1167
Link: Added: This issue related JBESB-1167
dependency jbesb-1167 resolved - In order to ensure we don't have multiple versions of hibernate, remove the hibernate3.jar from both jbpm and management console and use the hibernate3.jar in product/lib/ext to compile against. Since hibernate3.jar is already in default/lib in the server, we're okay to do this. Same version of Hibernate is available in the libs of default, production and the all configuration of EAP so the fix is okay here too