Bug 963516 - library version mismatch between brms-p-5.3.1.GA-deployable-ee6 and EAP6
library version mismatch between brms-p-5.3.1.GA-deployable-ee6 and EAP6
Status: NEW
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Build Process (Show other bugs)
BRMS 5.3.1
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Julian Coleman
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-15 23:08 EDT by Toshiya Kobayashi
Modified: 2013-05-15 23:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 963518 963519 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
jBPMEx81_getTasksAssignedAsPotentialOwner_GroupId_JPA2.zip (59.52 KB, application/zip)
2013-05-15 23:10 EDT, Toshiya Kobayashi
no flags Details

  None (edit)
Description Toshiya Kobayashi 2013-05-15 23:08:29 EDT
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.

https://hibernate.atlassian.net/browse/HHH-5310 

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.
Comment 1 Toshiya Kobayashi 2013-05-15 23:10:07 EDT
Created attachment 748567 [details]
jBPMEx81_getTasksAssignedAsPotentialOwner_GroupId_JPA2.zip

Note You need to log in before you can comment on or make changes to this bug.