Using Java in the assembly editor
Most of the time you deal with WSDL interfaces and references when working with components and imports in the assembly diagram. However, IBM® Integration Designer supports some Java™ functions and provides some ways for you to use Java components with your WSDL components. Java components, components with no implementation, and stand-alone references can have Java or WSDL interfaces in their partner references.
IBM Integration
Designer is organized around the use of WSDL interfaces and references, but it does provide some ways to work with Java:
- You can create a Java component.
- You can add a Java reference to a Java component or stand-alone references to invoke a target service that has a matching WSDL interface. To help you with this action, you can convert a WSDL reference on a Java component or on stand-alone references to a Java reference.
- You can drag a Java class onto the assembly editor canvas as a component or drag an EJB (stateless session bean) as an import. The assembly editor can generate a map component that allows you to invoke the Java component or import from a WSDL component.
Limitations of Java components in mediation modules
- When you wire a mediation flow component to a Java component, the service message object is not propagated through the Java component. As a result, an import invoked via the Java component will not have any transport headers that are set inside the mediation flow component.
- You cannot wire a Java component's reference to the interface of a mediation flow component.
The topics listed below provide information about these processes.