Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335829 - Cannot execute workflows defined with expanded BPEL designer
Summary: Cannot execute workflows defined with expanded BPEL designer
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Smila (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Juergen Schumacher CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 05:52 EST by Igor Novakovic CLA
Modified: 2022-07-07 11:31 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Novakovic CLA 2011-01-31 05:52:21 EST 
While trying to run workflows defined with the expanded BPEL designer (https://bugs.eclipse.org/bugs/show_bug.cgi?id=332926) I run into a problem. Namely, the BPEL designer correctly places the name of the extension activity' workflow step into the invokeService tag and not into the extensionActivity tag itself (as defined in our current workflow definitions). The problem is that our current BPEL integration layer has problems with it.
When SMILA starts (during the pipeline deployment) the following exception is being thrown:

2011-01-26 19:32:53,069 ERROR [Component Resolve Thread (Bundle 5)          ]  bpel.ODEWorkflowProcessor                     - Start of BPEL workflow service aborted: Unknown error.Service is non-functional, please fix problem and restart bundle
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
      at java.lang.String.substring(Unknown Source)
      at java.lang.String.substring(Unknown Source)
      at org.eclipse.smila.processing.bpel.ProcessingServiceManager.doRegisterActivity(ProcessingServiceManager.java:83)
      at org.eclipse.smila.processing.bpel.ProcessingServiceManager.doRegisterActivity(ProcessingServiceManager.java:1)
      at org.eclipse.smila.processing.bpel.ExtensionManager.registerActivity(ExtensionManager.java:94)
      at org.eclipse.smila.processing.bpel.SMILAExtensionBundle$InvokeServiceActivity.validate(SMILAExtensionBundle.java:152)
      at org.apache.ode.bpel.compiler.v2.ExtensionActivtityGenerator.compile(ExtensionActivtityGenerator.java:54)
…
Comment 1 Juergen Schumacher CLA 2011-01-31 06:27:47 EST 
Fixed for me. I've changed this line and similar one in PipeletManager not to assume a special format of the name anymore and changed all BPEL files accordingly. However, it should still work with BPEL files written the old way. The notable difference is just the name of the pipelet/service invocation in the JMX tree. For example, it was something like:
  $Service/PipeletName@line-$xy
now it is
 $Service/PipeletName@$name-attribute-of-invoke*-Element
If the name is not set there, the default name will be "extensionActivity-activity-line-$xy". So you should probably adapt your BPEL files and move the names to one line below (:
Comment 2 Andreas Weber CLA 2013-04-15 11:49:28 EDT 
Closing this