Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1145796 - Unable to save a "Test Scenario" that makes use of "Call Method" in BRMS 6
Unable to save a "Test Scenario" that makes use of "Call Method" in BRMS 6
Status: VERIFIED
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central (Show other bugs)
6.0.2
Unspecified Unspecified
high Severity high
: ER2
: 6.1.0
Assigned To: Toni Rikkola
Jiri Locker
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-23 15:12 EDT by Amana
Modified: 2014-12-02 05:53 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1203783 None None None Never

  None (edit)
Description Amana 2014-09-23 15:12:43 EDT
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:
Comment 8 Toni Rikkola 2014-10-30 12:24:55 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.