 | Warning
This component has been deprecated in favor to the Apache Ode Service Engine. |
servicemix-bpe
The servicemix-bpe Service Engine is a BPEL engine based on a Sybase donation to Apache ODE project.
Take a look at the bpel-bpe demo that ships with 3.x distributions.
Installation
Installing the servicemix-bpe component can be done in several ways:
- drop the installer zip in an hotdeploy directory monitored by ServiceMix
- using ant tasks
Note that when using ant tasks, the component is not started, you will have to start it manually using ant tasks or a console.
Configuration
You can use JNDI to customize servicemix-bpe configuration.
TODO
BPEL deployment
Service units targeted at servicemix-bpe should contain:
- a process definition in a file with a bpel extension
- the associated wsdl (same file name, but with a wsdl extension)
- other resources imported from these files (wsdls, xsds, etc...)
Lightweight mode
The servicemix-bpe component can also be configured in a spring/xbean configuration file, for use in an embedded ServiceMix.
Here is an example of such a configuration:
<sm:activationSpec>
<sm:component>
<bpe:component bpelResource="classpath:loanbroker/loanbroker.bpel" />
</sm:component>
</sm:activationSpec>
| Classpath issues when embedding servicemix-bpe component
When using the servicemix.xml configuration file to create bpel endpoints, you must include all the needed jars in your classpath.
You will find these files inside the component installer (./components/servicemix-bpe-xxx.zip).
Failing this, an IllegalArgumentException will be thrown with the following message:
Component name: xxxxxx is bound to an object which is not a JBI component, it is of type: javax.xml.namespace.QName |
