HP Integrity NonStop J-Series - Manual (Page 290)

Figure 98 Axis2/Java Contract-First Implementation
At design time, you can use the WSDL2Java tool, which accepts a WSDL file as input, and
generates the service skeleton files, client stubs (optional), and service configuration files based
on the specifications in the WSDL file.
The generated service skeleton files include Java classes that the service requires to interface
with the Axis2/Java server. Thereafter, you need to implement the business logic and build a
web archive file, which can then be deployed as a web service.
The web service deployed under NSJSP can be accessed using any SOAP clients on or outside
the NonStop platform. These SOAP clients can be developed using the client stubs generated
using the WSDL2Java tool or any other SOAP client development methodologies.
The WSDL2Java can also be used to generate SOAP client stubs in Java, based on the WSDL
file. The generated client stubs include classes to generate the SOAP message in the SOAP
request, consume the SOAP response, and send the SOAP request. You need to implement
the client business logic in the client.
For more information on creating web services and clients using the Contract-First approach,
see
“Getting Started with Axis2/Java” (page 319) .
2.
Exposing plain Java class as web service
Axis2/Java enables you to expose plain Java class as web services.
Figure 99 shows a typical scenario of design time activities, deployment tasks, and exposing
web services using Axis2/Java.
290 Axis2/Java Overview