Extending BPELUnit

BPELUnit contains various extension points and API. This section contains instructions for setting up an environment for working with the BPELUnit source code, developing extensions and clients.


Installing the source

The BPELUnit source is available via anonymous CVS in the form of Eclipse plugins. To download the plugins in Eclipse, do the following:

After the checkout completes, you will have the following new plugins in your Eclipse workspace:

Project Name Contents
org.bpelunit.framework The core BPELUnit framework.
org.bpelunit.framework.client.command The command line client


The Ant client
org.bpelunit.framework.client.eclipse The Eclipse client
org.bpelunit.toolsupport The BPELUnit Eclipse Tool Support
org.bpelunit.oracleUnDeployer The Oracle UnDeployer
org.bpelunit.howtobuild Information on the build process
org.bpelunit.build.eclipse The Eclipse feature
org.bpelunit.build.standalone Standalone build scripts

When making changes to this source code, or adding new clients in the form of additional Eclipse plugins, the complete source may be tested by using the Eclipse runtime workbench mechanism, or the included Java/Ant runners.

There are two things to keep in mind:

Developing extensions

As laid out in the thesis, extensions like new SOAP Encoders, Deployers, or Header Processors are developed against the framework core, but registered in a client-specific way. To add and test an extension with all three clients, you should take the following approach:

You may then run the Eclipse client in a runtime workbench, and the command line and ant clients from within Eclipse, to test the new extension.

Using the API

To create a new client, first have a look at the three existing clients and the way they use the BPELUnit API described in the thesis. To create new client, follow these steps: