| Summary: | Drools-persistence needs jbpm-persistence | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Tomas Schlosser <tschloss> |
| Component: | BRE (Expert, Fusion) | Assignee: | John Graham <jgraham> |
| Status: | VERIFIED --- | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | BRMS 5.2.0-Dev1 | CC: | jgraham, jlocker, lpetrovi, mproctor, rzhang |
| Target Milestone: | --- | ||
| Target Release: | BRMS 5.2.0.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/BRMS-617 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 724803 | ||
| Bug Blocks: | |||
|
Description
Tomas Schlosser
2011-06-30 07:11:31 UTC
Link: Added: This issue depends JBRULES-3053 I didn't see jbpm-persistence-jpa.jar existed in Drools-5.2.0.Final either. No, it wasn't there, but the dependency wasn't there either. I just tried removing all jbpm-*.jar from BRMS-5.2.0-DEV3 and the exception is gone. Problem probably is that Drools-5.2.0.Final doesn't contain any jbpm libraries, but BRMS contains some of them so it expects to have jbpm-persistence as well. The 4 jbpm-*.jar (not including jbpm-persistence-jpa.jar) in BRMS 5.2.0-Dev3 are included by drools-camel and drools-camel-server dependencies. Not sure we could exclude them in the release. Could we not exclude drools-camel*? According to ERD Drools Execution server support is deffered (see ERD: BRMS-PR-05). Yes, you are right, that feature is deferred. I will exclude drools-camel* in next brms-p ER1 build. jbpm-bpmn2,jbpm-flow-builder, jbpm-flow will still be included as guvnor-webapp's dependencies and drools-pipeline's dependencies. Compare to BRMS-5.2.0-dev3, only jbpm-workitems are excluded in drools-engine. This issue might still need further investigation. Link: Added: This issue is incorporated by BRMS-644 This issue conflicts with Bug 727562 here. It seems that we can't get away with jbpm-flow and jbpm-flow-builder in BRE. jbpm-persistence will need to be added. Prakash has already agreed to this. If there are no jBPM jars, Drools will persistence without jbpm-persistence. The moment there is jbpm core/builder on the path it'll need jbpm persistence. Marked as release note not required as this appears to be an issue between dev builds. Ryan, please add jbpm-persistence jar to the build. That is the only viable way this issue can be resolved. And what will be supported in this release is only drools persistence.. Please add this to ER3. Yes, this has been added in ER3. I am preparing to pass the ER3 to QE. In ER3 jbpm-persistence was added and the problem is gone. |