Bug 920507
| Summary: | Verification does not work if the package contains a DSL rule (.dslr) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jiri Locker <jlocker> | ||||
| Component: | BRM (Guvnor) | Assignee: | manstis | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.1 | ||||||
| Target Milestone: | --- | ||||||
| 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:34 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: | |||||||
| Attachments: |
|
||||||
This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Created attachment 708853 [details] server.log Description of problem: If the rule package contains a dslr rule, the attempt to verify any rule in that package fails with server-side exception and the client is presented with an error message saying "500 The call failed on the server; see server log for details". Version-Release number of selected component (if applicable): BRMS 5.3.1.GA How reproducible: always Steps to Reproduce: 1. get the sample mortgage repository installed 2. open any business rule, run verification to see it works OK 3. create new DSL Business Rule in mortgages package and save it as is 4. get back to the business rule and run verification again, it fails Actual results: Error message pops up in guvnor, server log contains exception. Expected results: Verification has to finish and present a verification report. Additional info: see attached server.log