Deployment Requirements for a Java (POJO) Endpoint
Deployment Requirements for a Java (POJO) Endpoint
Select the Java class that will be created and invoked at runtime.
For details on EJB Service, see
Deployment Requirements for Java (EJB) Endpoint
.
After you develop a BPEL process with a WSDL based on a Java interface, you're ready to deploy by creating JAR files. You will then provide deployment details specific to the Java interface. When you create the Process Deployment Descriptor (PDD) file for the process, you must provide details for the Java class that is created and invoked at runtime.
To provide required POJO deployment details:
Open the PDD Editor, as described in
Creating a Process Deployment Descriptor File
.
On the Partner Links tab, select the partner role that invokes the Java interface.
Notice that the selection is set to Java Service for the invoke handler.
In the
Java Invoke Handler Properties
dialog, select the Java class that is created and invoked at runtime.
Select the Java classpath to be used when instantiating and invoking the Java class. The classpath includes not only the JAR (or local "src" workspace directory) that contains the class being invoked, but also any JARs that contain classes referenced directly or indirectly by that class.
Note that the Inherit server classloader checkbox is selected by default. If you disable this option, you will only have access to the JARs on your classpath, not the JARs that are deployed to the server. You can also select Parent classloader last when inheriting Process Server classloader.
Deployment Details
When you select a Java invoke handler for the partner role implementing the Java interface, the Java resources are added to the resource catalog and deployed with the process. This includes all of the JARs included in the classpath.
Also, there is no endpoint reference information needed for a Java service.