Java

A Web service that has been compiled into classes can be used without modification, provided that the types of any arguments to the methods in the web service are supported by the Axis engine. Refer to Axis documentation for further details.

If the service uses a complex object as an argument, or returns one, that object must comply to the Java Bean specification.

The supplied deployment utility does not support the case where a service returns an object in a different package to the service itself. If you wish to do this, we can write your own deployment utility based on the supplied sample, or capture the commands produced by the supplied utility, using the -v option, and amend them to produce a tailored script.

If the service uses classes that are external to the Axis infrastructure and the SOAP/WebSphere MQ run time environment, amend the generated script that starts or defines the listeners, changing the CLASSPATH to include the services required. We can do this in any of the following ways:

• Amend the CLASSPATH directly in the script after the call to amqwsetcp.

• Create a service-specific script to customize the CLASSPATH and invoke this script in the generated script after the call to amqwsetcp.

• Create a customized deployment process to customize the CLASSPATH in the generated script automatically.