Bug 918682
| Summary: | Unable to identify what process has invalid data | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Amana <ajuricic> | ||||||||||||||
| Component: | BRM (Guvnor) | Assignee: | Kris Verlaenen <kverlaen> | ||||||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Marek Baluch <mbaluch> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | BRMS 5.3.1 | CC: | ajuricic, alazarot, kris.verlaenen, nwallace, tpothine | ||||||||||||||
| Target Milestone: | GA | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2025-02-10 03:27:33 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: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Bug Depends On: | |||||||||||||||||
| Bug Blocks: | 1022758, 1080634 | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Amana
2013-03-06 18:03:10 UTC
Do we know which brms version will include this fix ? I am not able to reproduce this issue (I've tried using BRMS 5.3.1 Roll Up Patch #3, but only the second process fails when compiling - as expected). Do you have any repository export that could be used in this BZ exposing the issue? Created attachment 820362 [details]
repository_export
There are two processes in defaultPackage.
-test1: it is trying to instantiate "Blue" , but it does not exist.
-test2: it is only printing a message.
The "Blue cannot be resolved to a type Blue" error is thrown for both processes by building the package. If you correct "test1" you will see that the error is not thrown anymore.
Created attachment 820363 [details]
screenshot
Thanks, reproduced. VERIFIED on BRMS_5.3.1_4 The original issue is fixed. The error will now be shown only for the process which contains the missing 'Blue' class. One minor issue (not reported) in this BZ still remains. If both processes contain the 'Blue' class script then the error message will be shown for both processes which is correct. The issue is that it will be shown 3 times all together. I believe there should be only 2 error messages. Created attachment 897341 [details]
wrong error message
Created attachment 897342 [details]
Test process 1 to repro the issue
Created attachment 897343 [details]
Test Process 2 to repro the issue
Created attachment 897886 [details]
4 processes, 1 error in each
Confirmed. I tried to create more processes with errors. On this screenshot I have test{1..4} processes using undefined Red, Green, Blue, Black types respectively. Obviously, the errors are _accumulated_ as the build iterates over resources so the last process "contains" all of the errors found in the preceding processes.
Added additional fix in drools 5.3.x http://github.com/droolsjbpm/drools/commit/d04da9ef5 Verified on Roll Up Patch BRMS_5.3.1_1_2014. This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |