Although most of the time you deal with WSDL interfaces and references
when working with components and imports in the assembly diagram, the Service
Component Architecture (SCA) programming model also supports Java™ interfaces.
WebSphere Integration Developer makes it easy for you to import a Java class
(implementation) or EJB (session bean) into your workspace and wire it into
your module assembly.
This task applies only to situations where you are doing bottom-up
development. You can find out more about bottom-up development in the topic
about that subject. See the related concepts below.
Most components in the assembly diagram use WSDL interfaces and references.
If such a component needs to call a Java implementation or an EJB import that
has a Java interface,
you will not be able to wire the source component's WSDL reference
directly to the session bean import that has the Java interface. However, WebSphere Integration
Developer generates a bridge component with a Java reference and a WSDL interface
to make it easy for you to complete the wiring. Here are the step-by-step
instructions:
- Locate the existing Java implementation that you want to use in
the Business Integration view or the Java Package Explorer view.
- Drag your Java component into your assembly diagram.
- The program prompts you to create a facade component. Click Yes. The program automatically adds a bridge component with a Java reference
and a WSDL interface. The following detail from the assembly diagram shows
a Java component,
Bridge, that is wired to a session bean import, SLSBImport:

- You can now draw a wire from the business process component to
the WSDL interface of the bridge component in the assembly. The
editor will create a matching WSDL reference on the service component to complete
the bridge.
The following assembly diagram shows that the BusinessProcess component
is wired through the bridge component to the SLSBImport Java import:
