Bug 1145796
| Summary: | Unable to save a "Test Scenario" that makes use of "Call Method" in BRMS 6 | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Amana <ajuricic> |
| Component: | Business Central | Assignee: | Toni Rikkola <trikkola> |
| Status: | CLOSED EOL | QA Contact: | Jiri Locker <jlocker> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.2 | CC: | etirelli, kverlaen |
| Target Milestone: | ER2 | ||
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-27 20:07:31 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: | |||
master: https://github.com/droolsjbpm/drools/commit/ffa9ae2d4 6.2.x https://github.com/droolsjbpm/drools/commit/52d742fad Problem was that the CallMethod class could not be pushed into the server side using the Errai, because the class was not marked as an Errai portable class. Unfortunately the fix requires recompiling all the GWT client side to work. Replacing the jar in the workbench war is not enough. |
Description of problem: The following exception is experienced when trying to save a 'Test Scenario' that makes use of 'Call Method': "Unable to complete your request. The following exception occurred: no marshalling definition available for type:org.drools.workbench.models.testscenarios.shared.CallMethod." Version-Release number of selected component (if applicable): BRMS 6.0.2 How reproducible: Always Steps to Reproduce: 1. create a project; 2. create a test scenario; 3. add "Number" class to test scenario from Config tab; 4. add to test scenario in Given a Number n; 5. add any method from Number using Call Method; 6. save test scenario and see the exception. Actual results: Unable to save and exception is experienced. Expected results: It should work. Additional info: