Bug 778953 (SOA-1384) - Support BpmProcessor in a synchronous manner
Summary: Support BpmProcessor in a synchronous manner
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-1384
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-23 02:55 UTC by Taro Yasuma
Modified: 2010-01-07 15:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-07 15:49:35 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1384 0 None Closed Support BpmProcessor in a synchronous manner 2012-02-22 14:56:28 UTC

Description Taro Yasuma 2009-06-23 02:55:55 UTC
Date of First Response: 2009-06-23 04:02:08
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/284823
project_key: SOA

AS-IS)
Assume using BpmProcesser on a ESB service to call a jBPM process. Then operation of BpmProcessor completes without return value from jBPM process instance(it only returns the original message).

TO-BE)
The usecase here is that using BpmProcessor in MEP=RequestResponse ESB service and it would be expected to get
any return value from jBPM process instance. For example, ithe following behaviours on ESB would be expected:

1. BpmProcessor is called in ActionPipeLine on ESB service,
2. jBPM process instance starts by the call in step#1,
3. One(or more) process variable is set in the jBPM process instance,
4. jBPM process is ended,
5. BpmProcessor gets and returns one(or more) value of the process value set in step#3 and
6. Next Action in ActionPipeLine gets the return value got in step#5.

Comment 1 Taro Yasuma 2009-06-23 03:00:51 UTC
Link: Added: This issue depends JBESB-2629


Comment 3 Kevin Conner 2009-06-23 08:02:08 UTC
Associated ESB task has been rejected.


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