| Summary: | Binary Drools packages created with SOA 5.0 don't work with SOA 5.1 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Lukáš Petrovický <lpetrovi> | ||||||
| Component: | Documentation, JBoss Rules | Assignee: | David Le Sage <dlesage> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 5.1.0.ER3 | CC: | darran.lofthouse, ldimaggi, tsurdilo | ||||||
| Target Milestone: | --- | Keywords: | Regression | ||||||
| Target Release: | 5.2.0 GA | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-2454 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: |
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.1) (fedora-44.1.9.1.fc14-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b06, mixed mode)
|
|||||||
| Last Closed: | 2011-11-14 17:46:17 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Lukáš Petrovický
2010-10-21 08:14:53 UTC
Attaching a package that was created using Drools 4.x and demonstrates the issue in SOA-P 5.1. Attachment: Added: defaultPackage.pkg Workaround Description: Removed: Just re-build the package with the latest Drools and it works. Added: Just re-build the package with the latest Drools and it should work. (Not tested unfortunately, since we don't have the source file for this particular package.) Investigate for SOA 5.1.0 Link: Added: This issue related BRMS-430 From ERD that has been approved: SOA-MGUP-1 Existing SOA Platform 5.0 users will be able to upgrade to SOA-P 5.1. No migration will be required. Upgrade is considered a fresh install of SOA Platform and a redeploy (no recompilation required) of customer applications/artifacts. Drools does not support forward or backwards compatability of any serialised formats. For this reason the rebuild button was added to Guvnor. It is also why the client version must be the same version as Guvnor, you cannot mix and match versions. See Mark's comment above. We need to be certain to document the migration/backward compatibility paths that we support - and that users must recompile per Mark's comment. Affects: Added: [Documentation (Ref Guide, User Guide, etc.)] Assigning to Darrin Mison as this is moving to a Doc Jira. Affects: Removed: [Documentation (Ref Guide, User Guide, etc.)] Added: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] I have now confirmed that the problem exists with packages created with Drools 5.0. Attachments coming soon. Attaching a package generated with BRMS 5.0 (= Drools 5.0). Steps for obtaining this package: 1) Log into BRMS. 2) Import sample repository. 3) Convert "defaultPackage" into a binary package. 4) Use the binary file inside SOA-P. Attachment: Added: defaultPackage_test.pkg Binary compatability is not kept for any different releases of major or minor, except possible minor.mionor; but either way we say that you must run with the same version jars on client and server and if you drop in new jars to the server regardless of the release then do a rebuild of packages. This is something we have been preaching to customers as well from the support side since BRMS 5.0 came out - when they upgrade they have to upgrade both sides in order to stay supported....so why this is now an issue i have no clue. Nobody is disputing what drools, as a project does, but this is an issue that needs to be discussed/resolved at the platform level. Just to clarify, as I've already received such question via e-mail: As a consequence of this issue, users upgrading to BRMS 5.1 will no longer be able to use its packages inside SOA 5.0. Inbetween BRMS 5.1 and SOA 5.1 releases, there will be a period of time where "latest BRMS" and "latest SOA" are incompatible. Not sure if this use case is relevant to our customers, though. Link: Added: This issue related SOA-2558 will be documented as a known issue in the SOA 5.1.0 release notes Release Notes Docs Status: Added: Not Yet Documented Writer: Added: Darrin Labels: Added: release_notes Affects: Removed: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)] Added: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] Writer: Removed: Darrin Added: dlesage Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2454 JBoss Rules does not support forward- or backward-compatability of any serialised formats. Versions of packages created in JBoss Rules 4.x are binary-incompatible with versions created in JBoss Rules 5.x For this reason the rebuild button was added to Rules. It is also why the client version must match the JBoss Rules version. To work around this problem, you must run with the same versions of the JARs on both the client and the server and, if you add news JARs to the server (regardless of the release) you must rebuild the packages. Release note created. |