Process Developer

Back Next

Creating a Java Interface

Process Developer provides an easy way for Java developers to use existing Java projects to build Java endpoints in a BPEL process. Your project can include a POJO (plain old Java object) or EJB. (A JavaBean can be used for all application servers except for Apache Tomcat). You can either start with or build a package that includes an interface and a Java class that implements the interface.

Using one of the techniques that Process Developer provides, you can automatically generate a WSDL and schema from your Java interface. The WSDL includes the port type, operation, and messages to create receives, replies, and invokes.

Process Developer also provides built-in features to automatically include all the JAR and other files required for deployment to the server.

Stateless or Stateful Invokes

Using the Java Interface, you can easily create invoke activities in BPEL. These invokes can be stateless or stateful.

A stateless invoke means that each time the Java code is called from the BPEL process, a new instance of the Java class is instantiated.

A stateful invoke is based on a Java class that is marked implementing the

java.io.Serializable

marker interface. With a stateful invoke, the process uses the same Java instance throughout the lifetime of the partnerLink useing it. Multiple invokes on the same POJO partner link result in method calls on the same POJO instance.

For details, see:

Setting up Your Java Project in Process Developer

Constraints for your Java Project

Generating WSDL and Schema from a Java Interface

Generating Argument Names for Schema Elements

Updating Your Java Project and Your BPEL Process Concurrently

Deployment Requirements for a Java (POJO) Endpoint

Deployment Requirements for Java (EJB) Endpoint

Interfaces, Service References, and Local WSDL

Setting up Your Java Project in Process Developer

Constraints for your Java Project

Generating WSDL and Schema from a Java Interface