Most of the time you deal with WSDL interfaces and references in
mediation modules; mediation flow components must have WSDL interfaces and
references. However, WebSphere® Integration Developer supports some Java™ functions
and provides some ways for you to use Java components with your mediation flow
components
WebSphere Integration
Developer is organized around the use of WSDL interfaces and references, but
it does provide some ways to work with Java:
- You can use a Java component in a mediation module in one of two ways:
- By invoking a Java component from a custom mediation primitive in
the mediation flow implementation.
- By wiring a reference in the mediation flow component to a Java component
.
- You can embed a Java or Visual snippet in a custom mediation
primitive in the mediation flow implementation. In this case, the Java code
is contained in the mediation flow implementation and you do not need a Java component
in the mediation module.
- You can convert a WSDL reference on a Java component or on stand-alone references
to a Java reference.
- You can generate a Java reference on a Java component
or stand-alone references to invoke a target service that has a matching WSDL
interface.
- 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 will 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.
- When you invoke a Java component through a custom mediation primitive,
the service message object is only passed to the Java component as a parameter
if the entire service message (/) is specified as the
message root property in the custom mediation primitive. Even in this case,
the service message object is not passed beyond the Java component.
- You cannot wire an export directly to a Java component in a mediation module.
- 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.