[jboss-jira] [JBoss JIRA] Updated: (GPD-203) Add ESB Service Node: Notifier

[Bernd-Christoph Schwede (JIRA)]

     [ http://jira.jboss.com/jira/browse/GPD-203?page=all ]

Bernd-Christoph Schwede updated GPD-203:
----------------------------------------

    Attachment: patchjBPM-GDP-3.1.2_for_SOA_platform.txt

Hi,

as a proof of concept I've patched the GPD such that it can read and write processdefinition.xml
in the syntax required by JBoss SOA platform (instead of the community JBoss ESB).

Please note that this is rather a quick hack that just proves that GPD can be tweaked to control
JBoss SOA platform. It is no longer able to read/write the community edition's syntax.

Since Koen told me that both syntax versions are converging in the near future,
the problem itself should disappear soon.

Until then, this patch may help.

Cheers,
Bernd-Christoph

> Add ESB Service Node: Notifier
> ------------------------------
>
>                 Key: GPD-203
>                 URL: http://jira.jboss.com/jira/browse/GPD-203
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.1
>            Reporter: Burr Sutter
>         Assigned To: Koen Aers
>         Attachments: patchjBPM-GDP-3.1.2_for_SOA_platform.txt
>
>
> As background information: http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/docs/services/jBPMIntegrationGuide.odt
> The ESB Service Node currently uses/assumes the following action:
> org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler 
> This action assumes an async "callback" and allows the user to specify "output" or expected returned values.  There is an option for a timeout if the async callback doesn't arrive in a specified amount of time.
> For true, one-way, no callback invocations of ESB Services we have added the ESBNotifier action:
> <node name="ShipIt">
>   <transition name="ProcessingComplete" to="end">
>   <action name="ShipItAction" class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbNotifier">
>    <esbCategoryName>BPM_Orchestration4</esbCategoryName>
>    <esbServiceName>ShippingService</esbServiceName>
>    <bpmToEsbVars>
>      <mapping bpm="entireCustomerAsObject" esb="customer" />
>      <mapping bpm="entireOrderAsObject" esb="orderHeader" />
>      <mapping bpm="entireOrderAsXML" esb="entireOrderAsXML" />
>     </bpmToEsbVars>
>    </action>
> </transition>
> </node>
> The designer should be enhanced so that the user can specify a one-way or two-way invocation.  We can discuss the exact terminology in the comments or a forum posting.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira