Generating Web Services for Java

You can generate client side or server side implementation classes, interfaces, deployment descriptor, JAR, WAR, or EAR from the Generate object language command in the Language menu.

Web services server side code generation consists in generating the following items:

Generate Web service implementation classes and interfaces (Java class, Stateless Session Bean, Servlet, etc.)
Generate Web services deployment descriptor for Java using the Web Service for J2EE (JSR109) specification. The deployment descriptor is an XML file that must be in every WAR archive, it is named WEB.xml by convention and contains information needed for deploying a Web service
Generate interface WSDL and implementation WSDL files (WSDL files can be generated separately because they can be used for UDDI or client applications)

In general, once a Web service is deployed, the server is capable of generating an implementation WSDL.

Web services client side code generation consists in generating proxy classes.

PowerDesigner supports several Web service implementation types in Java:

JAXM: http://java.sun.com/xml/jaxm/index.html
JAX-RPC: http://java.sun.com/xml/jaxrpc/index.html
Web Service for J2EE (JSR 109): http://www.jcp.org/en/jsr/detail?id=109
AXIS RPC and EJB and Java Web Service (JWS): http://ws.apache.org/axis/

Generating JAXM Web Services
JAXM is a Java API for XML messaging that provides a standard way to send XML documents over the Internet from the Java platform.
Generating JAX-RPC Web Services
JAX-RPC is a Java API for XML-based RPC (Remote Procedure Calling protocol). It facilitates RPC over the Internet allowing XML formatted parameters to be passed to remote services and allowing XML formatted values to be returned.
Generating Stateless Session Bean Web Services
PowerDesigner supports the Web Services for J2EE specification that defines the programming model and runtime architecture for implementing Web services.
Generating AXIS RPC Web Services
If the Web service implementation type is AXIS RPC, PowerDesigner uses a Java class for implementation and Apache Axis for deployment.
Generating AXIS EJB Web Services
If the Web service implementation type is AXIS EJB, PowerDesigner uses a Stateless Session Bean for the implementation, an application server for EJB deployment and Apache Axis for exposing the EJB as a Web service.
Generating Java Web Services (JWS)
If the Web service implementation type is Java Web Service (JWS), PowerDesigner uses a Java class for implementation. The Java class will have the .jws extension.
Testing Web Services for Java
To test a Java Web Service, there are several methods:

Parent topic: Working with Web Services