While the @WebService annotation is sufficient for service enabling a Java interface or a Java class, it does not provide a lot of information about how the service will be exposed as a service provider. The JAX-WS programming model uses a number of optional annotations for adding details about your service, such as the binding it uses, to the Java code. You add these annotations to the service's SEI.
![]() | Tip |
|---|---|
The more details you provide in the SEI the easier it will be for developers to implement applications that can use the functionality it defines. It will also provide for better generated WSDL contracts. |
If you are using a SOAP binding for your service, you can use JAX-WS annotations to specify a number of the bindings properties. These properties correspond directly to the properties you can specify in a service's WSDL contract.
The @SOAPBinding annotation is defined by the javax.jws.soap.SOAPBinding interface. It provides details about the SOAP binding used by the service when it is deployed. If the @SOAPBinding annotation is not specified, a service is published using a wrapped doc/literal SOAP binding.
You can put the @SOAPBinding annotation on the SEI and any of the SEI's methods. When it is used on a method, setting of the method's @SOAPBinding annotation take precedence.
Table 2.2 shows the properties for the @SOAPBinding annotation.
Table 2.2. @SOAPBinding Properties
| Property | Values | Description |
|---|---|---|
| style |
| Specifies the style of the SOAP message. If RPC style is specified, each message part within the SOAP body is a parameter or return value and will appear inside a wrapper element within the soap:body element. The message parts within the wrapper element correspond to operation parameters and must appear in the same order as the parameters in the operation. If DOCUMENT style is specified, the contents of the SOAP body must be a valid XML document, but its form is not as tightly constrained. |
| use |
| Specifies how the data of the SOAP message is streamed. |
| parameterStyle [b] |
| Specifies how the method parameters, which correspond to message parts in a WSDL contract, are placed into the SOAP message body. A parameter style of BARE means that each parameter is placed into the message body as a child element of the message root. A parameter style of WRAPPED means that all of the input parameters are wrapped into a single element on a request message and that all of the output parameters are wrapped into a single element in the response message. |
[a] [b] If you set the style to | ||
Example 2.5 shows an SEI that uses rpc/literal SOAP messages.
Example 2.5. Specifying an RPC/LITERAL SOAP Binding with the @SOAPBinding Annotation
package org.eric.demo;
import javax.jws.*;
import javax.jws.soap.*;
import javax.jws.soap.SOAPBinding.*;
@WebService(name="quoteReporter")
@SOAPBinding(style=Style.RPC, use=Use.LITERAL)
public interface quoteReporter
{
...
}When the runtime maps your Java method definitions into XML operation definitions it fills in details such as:
what the exchanged messages look like in XML.
if the message can be optimized as a one way message.
the namespaces where the messages are defined.
The @WebMethod annotation is defined by the javax.jws.WebMethod interface. It is placed on the methods in the SEI. The @WebMethod annotation provides the information that is normally represented in the wsdl:operation element describing the operation to which the method is associated.
Table 2.3 describes the properties of the @WebMethod annotation.
Table 2.3. @WebMethod Properties
The @RequestWrapper annotation is defined by the javax.xml.ws.RequestWrapper interface. It is placed on the methods in the SEI. As the name implies, @RequestWrapper specifies the Java class that implements the wrapper bean for the method parameters that are included in the request message sent in a remote invocation. It is also used to specify the element names, and namespaces, used by the runtime when marshalling and unmarshalling the request messages.
Table 2.4 describes the properties of the @RequestWrapper annotation.
Table 2.4. @RequestWrapper Properties
| Property | Description |
|---|---|
| localName | Specifies the local name of the wrapper element in the XML representation of the request message. The default value is the name of the method or the value of the @WebMethod annotation's operationName property. |
| targetNamespace | Specifies the namespace under which the XML wrapper element is defined. The default value is the target namespace of the SEI. |
| className | Specifies the full name of the Java class that implements the wrapper element. |
![]() | Tip |
|---|---|
Only the className property is required. |
The @ResponseWrapper annotation is defined by the javax.xml.ws.ResponseWrapper interface. It is placed on the methods in the SEI. As the name implies, @ResponseWrapper specifies the Java class that implements the wrapper bean for the method parameters that are included in the response message sent in a remote invocation. It is also used to specify the element names, and namespaces, used by the runtime when marshalling and unmarshalling the response messages.
Table 2.5 describes the properties of the @ResponseWrapper annotation.
Table 2.5. @ResponseWrapper Properties
| Property | Description |
|---|---|
| localName | Specifies the local name of the wrapper element in the XML representation of the response message. The default value is the name of the method with Response appended or the value of the @WebMethod annotation's operationName property with Response appended. |
| targetNamespace | Specifies the namespace under which the XML wrapper element is defined. The default value is the target namespace of the SEI. |
| className | Specifies the full name of the Java class that implements the wrapper element. |
![]() | Tip |
|---|---|
Only the className property is required. |
The @WebFault annotation is defined by the javax.xml.ws.WebFault interface. It is placed on exceptions that are thrown by your SEI. The @WebFault annotation is used to map the Java exception to a wsdl:fault element. This information is used to marshall the exceptions into a representation that can be processed by both the service and its consumers.
Table 2.6 describes the properties of the @WebFault annotation.
![]() | Important |
|---|---|
The name property is required. |
The @OneWay annotation is defined by the javax.jws.OneWay interface. It is placed on the methods in the SEI that will not require a response from the service. The @OneWay annotation tells the run time that it can optimize the execution of the method by not waiting for a response and not reserving any resources to process a response.
Example 2.6 shows an SEI whose methods are annotated.
Example 2.6. SEI with Annotated Methods
package com.iona.demo;
import javax.jws.*;
import javax.xml.ws.*;
@WebService(name="quoteReporter")
public interface quoteReporter
{
@WebMethod(operationName="getStockQuote")
@RequestWrapper(targetNamespace="http://demo.iona.com/types",
className="java.lang.String")
@ResponseWrapper(targetNamespace="http://demo.iona.com/types",
className="org.eric.demo.Quote")
public Quote getQuote(String ticker);
}The method parameters in the SEI coresspond to the wsdl:message elements and their wsdl:part elements. JAX-WS provides annotations that allow you to describe the wsdl:part elements that are generated for the method parameters.
The @WebParam annotation is defined by the javax.jws.WebParam interface. It is placed on the parameters on the methods defined in the SEI. The @WebParam annotation allows you to specify the direction of the parameter, if the parameter will be placed in the SOAP header, and other properties of the generated wsdl:part.
Table 2.7 describes the properties of the @WebParam annotation.
Table 2.7. @WebParam Properties
The @WebResult annotation is defined by the javax.jws.WebResult interface. It is placed on the methods defined in the SEI. The @WebResult annotation allows you to specify the properties of the generated wsdl:part that is generated for the method's return value.
Table 2.8 describes the properties of the @WebResult annotation.
Table 2.8. @WebResult Properties
Example 2.7 shows an SEI that is fully annotated.
Example 2.7. Fully Annotated SEI
package com.iona.demo;
import javax.jws.*;
import javax.xml.ws.*;
import javax.jws.soap.*;
import javax.jws.soap.SOAPBinding.*;
import javax.jws.WebParam.*;
@WebService(targetNamespace="http://demo.iona.com",
name="quoteReporter")
@SOAPBinding(style=Style.RPC, use=Use.LITERAL)
public interface quoteReporter
{
@WebMethod(operationName="getStockQuote")
@RequestWrapper(targetNamespace="http://demo.iona.com/types",
className="java.lang.String")
@ResponseWrapper(targetNamespace="http://demo.iona.com/types",
className="org.eric.demo.Quote")
@WebResult(targetNamespace="http://demo.iona.com/types",
name="updatedQuote")
public Quote getQuote(
@WebParam(targetNamespace="http://demo.iona.com/types",
name="stockTicker",
mode=Mode.IN)
String ticker
);
}