Examples of specifying the javax.xml.ws.WebServiceRef annotation are as follows:

• Specifying the annotation in a field
  

  ... import javax.servlet.ServletException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import javax.xml.ws.WebServiceRef; import com.sample.AddNumbersImpl; import com.sample.AddNumbersImplService; public class TestClient extends HttpServlet { // An example of a service class // Inject a service class instance in a service class type field @WebServiceRef private AddNumbersImplService service; // An example of a port // Inject a port instance in a port type field @WebServiceRef(AddNumbersImplService.class) private AddNumbersImpl port; @Override public void init() { // You need not execute the following processes because the Application server injects a service class and a port before // starting the Web Service client //service = new AddNumbersImplService(); //port = service.getAddNumbersImplPort(); } @Override public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException { ...

• Specifying the annotation in the setter method
  

  ... import javax.servlet.ServletException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import javax.xml.ws.WebServiceRef; import com.sample.AddNumbersImpl; import com.sample.AddNumbersImplService; public class TestClient extends HttpServlet { private AddNumbersImplService service; private AddNumbersImpl port; @Override public void init() { // You need not execute the following process because the application server injects a service class and a port by using the // setter method when starting the application //service = new AddNumbersImplService(); //port = service.getAddNumbersImplPort(); } // An example of a service class @WebServiceRef public void setAddNumbersImplService(AddNumbersImplService service) { // Inject the service class instances into the service argument this.service = service; } // An example of a port @WebServiceRef(AddNumbersImplService.class) public void setAddNumbersImpl(AddNumbersImpl port) { // Inject the port instances into the port argument this.port = port; } @Override public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException { ...

When starting a J2EE application, configure the following settings to generate an instance of a Web Services client.

For a servlet

Specify the load-on-startup element in web.xml of the WAR file with a Web Services client. If you do not want to specify the load-on-startup element, generate the instances when running the first Web application. For details, see uCosminexus Application Server Web Container Functionality Guide .

For EJB

Set the pooling in Stateless Session Beans to enabled state. Generate the number of instances equivalent to the minimum pooling in Stateless Session Beans when starting a J2EE application. When not using the pooling in Stateless Session Beans, generate an instance when running the first J2EE application. For details, see uCosminexus Application Server EJB Container Functionality Guide.

Notes

In an environment where the Web Services client and Web Service to connect to, are both deployed to the same J2EE server, an error (KDJW40043-E) occurs while injecting ports or service classes when starting the J2EE server.

Troubleshooting if injection fails:

• In the wsdlLocation element of the javax.xml.ws.WebServiceRef annotation, specify the WSDL document stored locally by using the relative path or absolute path.
• Stop the J2EE application that has the Web Services client before you stop the J2EE server. Restart the J2EE server and then start the Web Services client.
• Deploy Web Service and the Web Services client on different J2EE servers. First, start the J2EE server on which Web Service is deployed and then start the J2EE server on which the Web Services client is deployed.
• Perform the settings such that you can reference the WSDL document that was locally stored when injecting a service class or a port, by using the catalog functionality.

When using the handler framework in a service class or port injected by specifying the javax.xml.ws.WebServiceRef annotation, set the handler chain by using the APIs. For the handler chain settings, see 36.9.2 Setting the handler chain in the Web Services client. We recommend that you configure the handler chain settings when initializing a Web Services client because you need to perform the settings for ports only once. You need not perform the handler chain settings for ports every time you invoke Web Service. You can use the following methods for initializing a Web Services client:

Implementing a Web Services client as a servlet

A method in which the init method or the javax.annotation.PostConstruct annotation is specified

Implementing a Web Services client as an EJB

A method in which the javax.annotation.PostConstruct annotation is specified

By concurrently specifying the javax.xml.ws.WebServiceRef annotation and the annotation for features in the port type fields or in the setter method for port type fields, you can enable the features of the port to be injected. The features will be enabled only if you specify the javax.xml.ws.WebServiceRef annotation in the fields in which the annotation for features is specified or in the setter method for the fields. You, however, cannot specify the annotation for features in the service class type fields or in the setter method for the fields.

When enabling the features, you can specify the following annotations in the ports. For annotations, see 16.2 Customized mapping from Java to WSDL.

• javax.xml.ws.soap.Addressing
• javax.xml.ws.soap.MTOM
• com.sun.xml.ws.developer.StreamingAttachment

You can use attachments in the MTOM/XOP specification format on the ports to be injected, if you enable the feature as follows:

• Example of specifying the annotation in a field
  

  ... import javax.servlet.ServletException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import javax.xml.ws.WebServiceRef; import com.sample.AddNumbersImpl; import com.sample.AddNumbersImplService; public class TestClient extends HttpServlet { // Enable the MTOM/XOP specification format attachment in the port to be injected @MTOM @WebServiceRef(AddNumberImplService.class) private AddNumbersImpl port; @Override public void init() { ... } @Override public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException { ...

• Example of specifying the annotation in the setter method
  

  ... import javax.servlet.ServletException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import javax.xml.ws.WebServiceRef; import com.sample.AddNumbersImpl; import com.sample.AddNumbersImplService; public class TestClient extends HttpServlet { private AddNumbersImpl port; @Override public void init() { ... } // Enable the MTOM/XOP specification format attachment in the port to be injected @MTOM @WebServiceRef(AddNumberImplService.class) public void setAddNumbersImpl(AddNumbersImpl port) { this.port = port; } @Override public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException { ...

We recommend that you change the request context properties of ports to be injected when initializing the Web Services client. You can use the following methods for initializing the Web Services client:

The method of implementing as a servlet

A method in which the init method or the javax.annotation.PostConstruct annotation is specified

The method of implementing as an EJB

A method in which the javax.annotation.PostConstruct annotation is specified

Notes

In the Web Services clients that share a single port across multiple threads, if you change the request context properties of the port while multiple threads are operating, communication errors might occur or invalid SOAP messages might be sent. Therefore, you must change the request context properties of the port that is shared across multiple threads before the shared threads start operating.

You can change the request context properties of a port in the Web Services client that is implemented as a servlet as follows:

...
import java.util.Map;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.WebServiceRef;
 
import com.sample.AddNumbersImpl;
import com.sample.AddNumbersImplService;
 
public class TestClient extends HttpServlet {
 
    @WebServiceRef(AddNumbersImplService.class)
    AddNumbersImpl port;
 
    @Override
    public void init() {
        // Set the request context during initialization
        Map<String, Object> context = ((BindingProvider)port).getRequestContext();
        context.put("com.cosminexus.jaxws.connect.timeout", 60000);
    }
    ...
}