Red Hat Bugzilla – Bug 963518
library version mismatch between brms-p-5.3.1.GA-deployable-ee6 and EAP6
Last modified: 2013-10-22 10:03:19 EDT
I have cloned this BZ from BRMS 5.3.1 for the same concern about packaging BPMS 6
+++ This bug was initially created as a clone of Bug #963516 +++
For instance, brms-p-5.3.1.GA-deployable-ee6 includes hibernate-core-3.3.2.GA.jar but JBoss EAP 6.0.0 includes hibernate-core-4.1.3.Final-redhat-1.jar and JBoss EAP 6.0.1 includes hibernate-core-4.1.6.Final-redhat-3.jar.
I'm under impression that brms-p-5.3.1.GA-deployable-ee6 should provide the same version jars as EAP 6 so that users can test with those jars and then deploy the application on EAP 6.
Actually, if I run jBPM5+JPA2 with jars under brms-p-5.3.1.GA-deployable-ee6/jboss-jbpm-engine/lib, I get the following Exception:
org.xml.sax.SAXParseException: cvc-complex-type.3.1: Value '2.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' has a fixed value of '1.0'.
which was fixed in hibernate 3.5.6.
If I switched hibernate libraries to ones in EAP 6.0.1 (hibernate 4.1.6) and it seems to work fine. (Attached an example project)
I confirmed with Lukas that jBPM5+JPA2 is supported/tested with EAP 6. So brms-p-5.3.1.GA-deployable-ee6 should be fixed.
--- Additional comment from Toshiya Kobayashi on 2013-05-15 23:10:07 EDT ---
Created attachment 748567 [details]
This issue might not be appliable or have alrealy been fixed in BPMS6.
Both product-depolyable or product-eap6 distribution is not using the old hibernate version anymore.
*** Bug 963519 has been marked as a duplicate of this bug. ***
This should not be an issue for BRMS/BPMS 6, because all libraries should be available as EAP modules.