If you want a Java™ component to invoke a component that
has a WSDL interface, the Java to WSDL conversion can be generated
by the assembly editor.
This task applies to situations where you are doing top-down development,
creating an assembly diagram before generating a business implementation.
You can find out more about top-down development in the topic about that subject.
See the related concepts below.
If you want to invoke a component that has a WSDL interface from
a Java component, follow these steps. You can use the same steps to invoke
a component that has a WSDL interface from stand-alone references that are
backed by Java code, such as a JSP.
- If you do not already have the service component in the assembly
diagram, create a component with no implementation type. When you wire from
a Java component to a target component that has a WSDL interface, a reference
will be created on the source Java component. During the wiring, you will
be asked if you want to generate a Java reference compatible with the target
WSDL interface, instead of generating a WSDL reference. By selecting this
option, you will be able to generate a Java reference on the source. This Java
reference allows you to use static methods rather than dynamic invocation
interface (DII) methods to interact with the target service. With this option,
two interfaces are generated: synchronous interfaces and asynchronous interfaces.
(The asynchronous interfaces will be created after the build run or when you
regenerate the implementation.)
- Click the Add Interface icon,
, on the component.
- In the Add Interface dialog box, select Show WSDL as
the interface type and select an existing interface or click New and
type a name for the interface in the Name field.
- From the palette, drag a Java component into your assembly diagram.
- Add an interface to your new Java component, selecting from the Show
Java list.
- Draw a wire from the component with the WSDL interface to the component
with the Java interface.
- Accept the creation of a matching reference on the source node.