uCosminexus Application Server, Web Service Development Guide
This subsection describes the functionality and specifications that you can use for developing SOAP Web services in Cosminexus. For details on the support range of the standard specifications, see the following sections:
The commands provided with the JAX-WS functionality of Cosminexus operate according to the default mapping of WSDL to Java that is defined in Chapter 2 of JAX-WS 2.2 specifications and according to the default mapping of Java to WSDL that is defined in Chapter 3 of JAX-WS 2.2 specifications.
Also, when the JAX-WS engine on the Web Service machine requires the WSDL that is the meta data for Web services, and if the WSDL does not exist in WAR files or EJB JAR files generate the WSDL according to the default mapping of Java to the WSDL defined in Chapter 3 of JAX-WS 2.2 specifications.
For the default mapping of the WSDL to Java, see the subsection 15.1 Default mapping of WSDL to Java. For the default mapping of Java to WSDL, see the subsection 16.1 Default mapping of Java to WSDL.
The commands provided with the JAX-WS functionality of Cosminexus operate according to the customized mapping (binding declaration) of the WSDL to Java that is defined in Chapter 7 of JAX-WS 2.2 specifications and according to the customized mapping (annotation) of Java to the WSDL that is defined in Chapter 8 of JAX-WS 2.2 specifications.
Also, when the JAX-WS engine on the Web Service machine requires the WSDL that is the meta data for Web services, and if the WSDL does not exist in WAR files or EJB JAR files, generate the WSDL according to the customized mapping of Java to the WSDL defined in Chapter 7 of JAX-WS 2.2 specifications.
For the WAR files, see 3.5.1 Configuring WAR files. For the EJB JAR files, see 3.5.2 Configuring EJB JAR files. For the customized mapping of the WSDL to Java, see 15.2 Customized mapping of WSDL to Java. For the customized mapping of Java to the WSDL, see 16.2 Customized mapping of Java to WSDL.
The JAX-WS engine of Cosminexus binds Java and the WSDL according to Chapter 2 and Chapter 3 of the JAX-WS 2.2 specifications for both Web services and Web Service clients.
For the support range of JAX-WS engines of Cosminexus, see 10.2 Operations of the JAX-WS engine.
The JAX-WS functionality of Cosminexus supports the WSDL of WSDL 1.1 specifications. Only the document/literal style is supported as the WSDL definition style. For the document/literal style, you can use both the wrapper style and the non-wrapper style.
For the support range of WSDL 1.1 specifications, see 19.1 Support range of WSDL 1.1 specifications.
The JAX-WS functionality of Cosminexus supports SOAP Messages of the SOAP 1.1 and SOAP 1.2 specifications.
The JAX-WS functionality of Cosminexus only supports the request-response operations and one-way operations as MEP. For details on how to define the request-response operations and one-way operations, see the following subsections:
For details on one-way operations and notes, see 10.22 One-way operations.
The JAX-WS functionality of Cosminexus does not support the functionality used for implementing asynchronous invocation of Web Service clients that are described in Section 2.3.4 and Chapter 4 of JAX-WS 2.2 specifications.
The JAX-WS functionality of Cosminexus supports the Dispatch interface described in Chapter 4 of the JAX-WS 2.2 specifications, the Provider interface described in Chapter 5 of the JAX-WS 2.2 specifications, and the functionality related to the Dispatch interface and Provider interface. However, among all the objects described in Chapter 4 of the JAX-WS 2.2specifications, the JAX-WS functionality does not support the following objects:
The JAX-WS functionality of Cosminexus does not support the functionality for dynamically creating and issuing the Web Service endpoints that are described in Chapter 5 of JAX-WS 2.2 specifications.
The JAX-WS functionality of Cosminexus supports the API-based dynamic handler settings for implementing Web Service clients. The functionality also supports the annotation-based dynamic handler settings for implementing Web services. The static settings assuming JSR-109 specifications are not supported.
The JAX-WS functionality of Cosminexus supports the attachments of the SAAJ 1.3 specifications, attachments with the format for coding the wsi:swaRef format in a WSDL, and attachments in the MTOM/XOP specification format. The functionality does not support coding that uses the MIME extension element of the WSDL 1.1 specifications (MIME binding). For using attachments in the wsi:swaRef format, see 28. Attachment Functionality (wsi:swaRef format). For using attachments in the MTOM/XOP specification format, see 30. Attachment Functionality (MTOM/XOP).
With the JAX-WS functionality of Cosminexus, the standard message context property described in Chapter 9 of JAX-WS 2.2 specifications is read-only. The functionality supports the property used for specifying a timeout when implementing Web services. For the usage and precautions for the message context, see the section 19.2.5 Using a message context.
The JAX-WS functionality of Cosminexus supports the APIs of the JAX-WS 2.2 specifications. For the support range of the JAX-WS APIs, see the section 19.2 Support Range of APIs.
The JAX-WS functionality of Cosminexus does not support the XML/ HTTP binding described in Chapter 11 of the JAX-WS 2.2 specifications.
For Web Services developed, starting from SEI, the JAX-WS functionality of Application Server supports the functionality of the JAX-WS engine (hereafter, also referred to as the functionality to dynamically generate wrapper beans) that dynamically generates JavaBeans classes of wrapper beans (request beans and response beans) and fault beans described in the section 3.6.2.1 and section 3.7 of the JAX-WS2.2 specifications. The Web service clients or Web Services that start from the WSDL do not support the functionality that dynamically generates wrapper beans.
For details on the functionality that dynamically generates wrapper beans, see 10.23 A functionality that dynamically generates wrapper beans.
The following points describe the related standard specifications:
Table 1-2 Items and support of WSEE (JSR-109) specifications
No. | Item | Support | |
---|---|---|---|
1 | The methods of Stateless session bean and singletone session bean are as follows:
|
Stateless | Y |
Singletone | -- | ||
2 | Client model. A method for detecting service interface by using JNDI and a method of using WebServiceRef annotation of JAX-WS specifications | Contents of the section 4.2.2 (service class and port injection) | Y |
Contents of sections other than 4.2.2 | -- | ||
3 | Deployment model. A method of packaging to EAR file and life cycle. | Contents described in section 5.4 | Y |
Contents other than those described in section 5.4 | -- | ||
4 | Deployment descriptor. The contents that must be coded along with WebServices.xml syntax and mapping with annotation that is defined in JAX-WS specifications (Web services Metadata (JSR-181) specifications). | -- | |
5 | Mapping with the existing Java EE container functionality such as role | -- |
This section describes the functionality and specifications you can use for developing RESTful Web Services (Web resource) with Cosminexus. For details on the support range of the standard specifications, see 24. Support range of the JAX-RS specifications.
A resource class is used for implementing Web resources. Chapter 3(8) of the JAX-RS 1.1 specifications defines resource classes. There are two types of resource class; root resource classes and sub resource classes.(8) The JAX-RS functionality of Cosminexus supports both the resource classes.
For details on root resource classes, see 17.1.1 Root resource class. For details on sub resource classes, see 17.1. 7 Sub resource class.
A provider is an extended functionality for the JAX-RS engine. Chapter 4 of the JAX-RS 1.1 specifications defines Provider. There are three types of providers; entity providers, context providers, and exception mapping providers.
An entity provider maps an HTTP entity body and a Java type. The JAX-RS functionality supports a built-in entity provider. For details on the MIME types and Java types supported by a built-in entity provider, see 17.1.1(4)(c) Entity parameter.
A context provider provides the context to a resource, or to the other resource providers. The JAX-RS functionality supports a built-in context provider. For details on the context supported by a built-in context provider, see 24.4 Context.
An exception mapping provider customizes the mapping between the Web resource exceptions and HTTP responses. For details on the exception mapping provider, see 17.2.2 Exception mapping provider.
The Application is a factory of the resource classes and providers. Chapter 2 of the JAX-RS 1.1 specifications defines the Application. The JAX-RS 1.1 specifications support a built-in Application. For details on the built-in Application, see 11.3.1 Configuration of WAR files.
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.