Writing the WSDL extension that lets your WSIF service invoke a method on a local Java object
Using the Web Services Invocation Framework (WSIF) Java™ provider, WSIF can invoke Java code. This means that, in a thin-client environment such as a Java virtual machine (JVM) or Tomcat test runtime environment, you can define shortcuts to local Java programs. Use this procedure to help you to write the Web Services Description Language (WSDL) extension that links your WSIF service to a local Java application.
Before you begin
The WSIF Java provider is not intended for use in a Java Platform, Enterprise Edition (Java EE) environment. There is a difference between a client using the WSIF Java provider to invoke a Java component, and implementing a web service as a Java component on the server side.
About this task
The WSIF Java binding exploits the format binding for type mapping. Using the format binding, your WSDL can define the mapping between XML schema types and Java types.
The WSIFJava provider requires the targeted Java classes to be on the class path of the client. The Java method is invoked synchronously, in-process, in-thread, with the current thread and Object Request Broker (ORB) contexts.
The WSIF Java provider is not transactional.
The WSIF Java provider does not support the WSIF synchronous timeout. The Java provider will not time out waiting for a Java method to complete.
Use the following procedure, and associated code fragments, to help you to specify the WSDL extension that enables your WSIF service to invoke a method on a local Java object.