JBossDeveloper

Hey Jeff,

The first pair of screen shots are the same page, the ony difference is that in the first, a couple of the sections are collapsed and in the second they are expanded.  As you can see, there is only one other page associated with the selected element, which is the standard "Description" page that is available for all nodes.  These properties are available on a SwitchYard "ServiceTask."  As for the process definition, it's simply Start->ServiceTask->End.  The process also has an interface definition (ExampleService) that was imported from a Java type (enhancement to the bpmn editor), along with operations, message references and item definitions for the types used.

The second screen shot is what you get when you select a custom "SwitchYard Service" Task.  This is the original integration with jBPM.  We've kept it around because it allows you to dynamically specify the service to invoke using process variables.  The other property pages are the standard "Description" and "I/O Parameters."  The former is the standard that comes with all tasks, while the latter is where you define DataInput, DataOutput and associations for them.  Once again, the process is simply Start->Task->End.

I hope to have this commited in the next few days.

Hope that helps,

Rob

Hey folks,

So, with the new ServiceTask support, here's the basic workflow:

1. On the process properties, select the "Interfaces" tab.  There is a new buton, "Import."  Import the interface associated with the service reference.
2. Drag the "SwitchYard Service Task" tool from the palette to your canvas.
3. On the "SwitchYard Service Task" tab, select the operation you wish to invoke in the drop list.
4. Map the Input, Output and Fault values as necessary.  The input can be either and expression or variable mapping.  Output and Fault must map back to a process variable.
5. Wire the task into your process and test.

For the "SwitchYard Dynamic Service Task," the process is a little different.

1. Drag the "SwitchYard Dynamic Service Task" tool from the palette to your canvas.
2. On the "SwitchYard Dynamic Service Task" tab, map values for the "Service Name" and "Operation Name"
3. On the "I/O Parameters" tab, create a DataInput whose name matches the value in "ContentInputName" (contentInput by default) and a DataOutput (if necessary) whose name matches the value in "ContentOutputName" (contentOutput by default).
4. Wire the task into your process an test.

(The dyanmic task looks like it has fewer steps, but step 1 and 2 are covered by step two in the service task and creating the I/O parameters is a bit more intensive than step 3 makes it sound.)

I'll update this thread once a build is available.

Best,

Rob

Jeff, can I please see your BPMN2 and switchyard.xml files?

Hey Jeff,

jBPM doesn't like if the item definitions aren't declared before the messages before the interfaces.  Open the bpmn in a text editor and reorder the elements so you have item definitions followed by messages followed by interfaces followed by the process.

Hope that helps,

Rob

Jeff,

Looking at your switchyard.xml, I see a couple things:

1. Your error, "Could not parse knowledge", is most likely because your PolicyQuoteCalculation component has no resources defined inside its manifest:

    <sca:component name="PolicyQuoteCalculation">

      <rules:implementation.rules>

        <rules:manifest/>

      </rules:implementation.rules>

      ...

should be:

    <sca:component name="PolicyQuoteCalculation">

      <rules:implementation.rules>

        <rules:manifest>

           <rules:resources>

             <rules:resource location="PolicyQuoteCalculation.drl" type="DRL"/>

           </rules:resources>

         </rules:manifest>

      </rules:implementation.rules>

      ...

2. You should remove this block completely:

        <bpm:workItemHandlers>

          <bpm:workItemHandler class="org.switchyard.component.bpm.work.SwitchYardServiceWorkItemHandler" name="SwitchYard Service"/>

        </bpm:workItemHandlers>

Not only did that WIH change package ( s/work/service/ ), but you don't need to register it yourself anymore. It gets auto-registered by the runtime.  You only have to include it in config if you want to override the WIH with that name.

Best regards,

David

When using the serviceTask, switchyard uses the BPMN2's interface implementationRef as the name to lookup as the switchyard service reference.

This is what you have in your BPMN2 file (see implementationRef attribute):

  <interface id="Interface_2" implementationRef="org.acme.insurance.PolicyQuoteEntityService.PolicyQuoteEntityService" name="PolicyQuoteEntityService">

    <operation id="Operation_2" implementationRef="storePolicyQuote" name="storePolicyQuote">

      <inMessageRef>PolicyQuoteEntityService_storePolicyQuote_policyquote</inMessageRef>

      <outMessageRef>PolicyQuoteEntityService_storePolicyQuote_Result</outMessageRef>

    </operation>

  </interface>

However, in your switchyard.xml, you only have just "PolicyQuoteEntityService"  (see the name attribute):

      <sca:reference name="PolicyQuoteEntityService">

        <sca:interface.java interface="org.acme.insurance.PolicyQuoteEntityService.PolicyQuoteEntityService"/>

      </sca:reference>

So, obviously these two attributes do not match, which leads us to an option, and a question:

1) Change one of those attributes to match the other.

2) I was told that the switchyard service name (more specifically, the switchyard service reference name) should be looked up using the BPMN2 interface element's implementationRef attribute.  Is this not correct?  Should it instead match on the BPMN2 interface element's name attribute?

I might be wrong about what I just said... These are input parameters that must be available to the serviceTask.  On your serviceTask, I don't see a

"interfaceImplementationRef" paramater defined at all....  The task handler will look for that first, and if it can't fine that, will default to looking for an "Interface" parameter.  You could try setting one of those to "PolicyQuoteEntityService".  Sorry for the confusion!

Hey guys,

I think we need to rework the component to use "Interface" and "Operation" as the keys instead of "interfaceImplementationRef" and...

Jeff, all you should have to do is change the implementation ref on the interface definition to match the SwitchYard service name (PolicyQuoteEntityService).

Hope that helps.

Rob