How to Use Web Service Annotations

To generate the WSDL file, the Enterprise JavaBeans interface must use the following web service annotations. Use of these annotations is described in JSR 224: Java API for XML-Based Web Services (JAX-WS) 2.0. Visit the following URL for details:

http://www.jcp.org/en/jsr/detail?id=224

In addition, only a document/literal WSDL is currently supported by the Enterprise JavaBeans binding layer.

Table 38-1 describes the annotations to use.

Table 38-1 Annotations

Name	Description
`@javax.jws.WebResult;` `@javax.jws.WebParam;`	Customizes the mapping of an individual parameter to a web service message part and XML element. Both annotations are used to map SDO parameters to the correct XML element from the normalized message payload.
`@javax.jws.Oneway;`	Denotes a method as a web service one-way operation that has only an input message and no output message. The Enterprise JavaBeans binding component does not expect any reply in this case.
`@javax.xml.ws.RequestWrapper;` `@javax.xml.ws.ResponseWrapper;`	Tells the Enterprise JavaBeans binding components whether the deserialized object must be unwrapped or whether a wrapper must be created before serialization. An Enterprise JavaBeans interface can be generated from an existing WSDL or obtained by some other means. If the WSDL does not exist, it can be generated.
`@javax.xml.ws.WebFault;`	Maps WSDL faults to Java exceptions. This annotation captures the fault element name used when marshalling the JAXB type generated from the global element referenced by the WSDL fault message.
`@oracle.webservices.PortableWebService`	Specifies the `targetNamespace` and `serviceName` used for the WSDL. For example: @PortableWebService( targetNamespace = "http://hello.demo.oracle/", serviceName = "HelloService") The `serviceName` is used as the WSDL file name. If it is not specified in the annotations, the service endpoint interface (SEI) class name is used instead.
Add appropriate method parameter annotations	Controls how message elements and types are mapped to the WSDL. For example, if your interface is in `doc/lit/bare` style, add the following annotations to the methods. @WebMethod @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
`@SDODatabinding`	Adds to the interface class to use the existing schema instead of a generated one. For example: @SDODatabinding(schemaLocation = "etc/HelloService.xsd")

The following example provides an example of an Enterprise JavaBeans interface with annotations.

@Remote
@PortableWebService(targetNamespace = "http://www.example.org/customer-example",
 serviceName = "CustomerSessionEJBService")
@SDODatabinding(schemaLocation = "customer.xsd")
public interface CustomerSessionEJB {
     @WebMethod(operationName="createCustomer")
   @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
   @WebResult(targetNamespace = "http://www.example.org/customer-example",
 partName = "parameters", name = "customer")
   CustomerType createCustomer();
     @WebMethod(operationName="addPhoneNumber")
   @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
   @WebResult(targetNamespace = "http://www.example.org/customer-example",
 partName = "parameters", name = "customer")
   CustomerType addPhoneNumber(@WebParam(targetNamespace =
 "http://www.example.org/customer-example", partName = "parameters", name =
 "phone-number")PhoneNumber phNumber);
}