Bug 1145796 - Unable to save a "Test Scenario" that makes use of "Call Method" in BRMS 6
Summary: Unable to save a "Test Scenario" that makes use of "Call Method" in BRMS 6
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER2
: 6.1.0
Assignee: Toni Rikkola
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 19:12 UTC by Amana
Modified: 2020-03-27 20:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:07:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1203783 0 None None None Never

Description Amana 2014-09-23 19:12:43 UTC
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 16:24:55 UTC
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.