| Summary: | XOR Split not working properly inside CompositeNode | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | nwallace <nwallace> |
| Component: | unspecified | Assignee: | Kris Verlaenen <kris.verlaenen> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Target Release: | 5.0.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/BRMS-170 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
java.version = 1.6.0_11
java.vm.name = Java HotSpot(TM) Client VM
Windows Vista Service Pack 1
|
|
| Last Closed: | 2009-09-01 12:24:36 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: | |
|
Description
nwallace
2009-07-07 14:36:20 UTC
Link: Added: This issue is related to JBRULES-2054 Fix in place. For documenting this in the Release Notes, can you please confirm the following and fill in the missing information. Dot point explanations are fine: The CAUSE (what was actually broken) * the "XOR split" functionality inside the CompositeNode was not working properly. CONSEQUENCES of the bug (how it impacts users.) * The FIX (what was changed to eliminate this bug) and * RESULTS of the fix (what now happens for users.) * The generation of rules for nested nodes has been fixed We are still awaiting the outstanding information for the Release Notes on this one. Please provide it as soon as possible. Thanks. The CAUSE (what was actually broken) * the "XOR split" functionality inside the CompositeNode was not working properly. CONSEQUENCES of the bug (how it impacts users.) * usage of an XOR split inside a composite node could lead to unexpected results The FIX (what was changed to eliminate this bug) and * XOR split now takes into account it can be part of a nested node RESULTS of the fix (what now happens for users.) * The generation of rules for nested nodes has been fixed |