JAX-WS2.0 specifications-Chapter 1: Introduction

Source: Internet
Author: User
Tags deprecated
Chapter1 Introduction

XML is a platform-independent representation of structured information. XML Web Services use XML to communicate with customers of network-based services and inherit XML platform independence. Soap describes the XML-based message format and "defines an extended message framework using XML technology. This framework contains a message structure that can be exchanged between various potential protocols ." WSDL is a set of endpoints that describe network services as a document-oriented or process-oriented information in XML format. "WSDL can be considered as the actual description language of XML Web Services. The JAX-RPC1.0 defines APIs and protocols for XML Web services that support RPC on the Java platform. JAX-RPC1.1 added support for WS-I basic profile1.0 to improve interoperability between JAX-RPC actuators and services implemented using other technologies. JAX-WS2.0 (the current specification) is a follow-up to the JAX-RPC1.1 and has made the following extensions to it: 1.1 targets since the release of JAX-RPC 1.0, the new specifications and new standard versions on which it depends are also released. As mentioned below, JAX-WS2.0 is related to these specifications and standards: JaxbJAX-RPC 1.0 defines its own data binding policy due to the relationship at the beginning. With the release of jaxb 1.0. There is no reason to maintain two separate XML ing rule sets on the Java platform. JAX-WS 2.0 delegates data binding-related tasks to the jaxb 2.0 specification, which is developed at the same time as JAX-WS 2.0. Jaxb 2.0The ing between Java and XML is added, and the XML schema structure is rarely used, and two-way custom binding between Java <--> XML data is provided. JAX-WS 2.0 will allow full use of jaxb's features including binding custom and optional schema verification. HTTP 1.2While soap 1.1 is still widely used and recommended by W3C, we can expect the service to be migrated to soap1.2. JAX-WS2.0 will support soap 1.1 when you need to continue to support soap 1.2. The WSDL 2.0During the existence of this JSR, W3C wants to accelerate the recommended solution for WSDL 2.0. WS-I basic profile 1.1JAX-RPC 1.1 added support for WS-I basic profile 1.0. WS-I basic profile 1.1 is intended to replace 1.0 when this JSR still exists and JAX-WS 2.0 will increase the support for additional interpretations it provides. Java The metadata function of the programming language ( Jsr175 )JAX-WS2.0 will define the use of Java annotations to simplify common development scenarios on the client and server. Based on Java Platform Web Service metadata (JSPs 109)Jsr109 defines the jaxrpc-maping-Info configuration descriptor to provide the ing between Java and WSDL during runtime deployment. Together with JSR 181, JAX-WS 2.0 uses runtime Java annotations that control mappings between Java and WSDL to implement this ing function. Web Service Security (Jsr183)JAX-WS 2.0 will be consistent with the security API defined by JSR (183) and implement it. JAX-WS 2.0 will improve the use of text/message-centric: Asynchronization ( Asynchrony )JAX-WS 2.0 will increase support for client asynchronous operations. Non -HTTP Transmission ( Non-HTTP transports )JAX-WS 2.0 will improve the XML Message format and underlying transport mechanism to simplify JAX-WS usage for non-HTTP transport. Message Access JAX-WS2.0This will simplify access to messages exchanged between the client and the server. Session management JAX-RPC 1.1Session management capability is tied to HTTP. JAX-WS 2.0 adds message-based session management.] JAX-WS 2.0 We will also propose JAX-RPC1.0 Problems arising from experience: Include in J2se  The JAX-WS2.0 will prepare a version of j2se that will be included in the JAX-WS. The portability of applications is a key requirement and JAX-WS2.0 will define mechanisms to generate completely portable client non-HTTP transfers.   HandlersJAX-WS 2.0 will simplify handlers development and provide a mechanism to allow handlers to collaborate with the implementation of service clients and service endpoints. Versioning and evolution ofWeb ServicesJAX-WS 2.0 will describe techniques and mechanisms to handle the burden on developers when creating new versions of existing services. 1.2 Non-TargetThe following are non-goals: Backwards compatibility of binary artifactsBinary Compatibility Between JAX-RPC 1.x and JAX-WS 2.0 implementation runtimes. Pluggable Data BindingJAX-WS 2.0 will defer Data Binding to jaxb [10]; it is not a goal to provide a plug-in API to allow other types of data binding technologies to be used in place of jaxb. however, JAX-WS 2.0 will maintain the capability to selectively disable Data Binding to provide an XML based fragment suitable for use as input to alternative data binding technologies. Soap encoding supportUse of the soap encoding is essential deprecated in the Web Services Community, e.g ., the WS-I basic profile [8] excludes soap encoding. instead, literal usage is preferred, either in the RPC or document style. soap 1.1 encoding is supported in JAX-RPC 1.0 and 1.1 but its support in JAX-WS 2.0 runs counterto the goal of delegation of Data Binding to jaxb. therefore JAX-WS 2.0 will make support for soap 1.1 encoding optional and defer description of it to JAX-RPC 1.1.support for the soap 1.2 encoding [4] is optional in soap 1.2 and JAX-WS 2.0 will not add support HTTP 1.2 encoding. Backwards compatibility of generated artifactsJAX-RPC 1.0 and jaxb 1.0 bind XML to Java in differentways. generating source code that works with unmodified JAX-RPC 1.x client source code isnot a goal. Support for Java versions prior to j2se 5.0JAX-WS 2.0 relies on collections of the Java language features added in j2se 5.0. It is not a goal to support JAX-WS 2.0 on Java versions prior to j2se 5.0. Service Registration and DiscoveryIt is not a goal of JAX-WS 2.0 to describe registration and discoveryof services via UDDI or ebXML RR. this capability is provided independently by jaxr [16]. plug-in API to allow other types of data binding technologies to be used in place of jaxb. however, JAX-WS 2.0 will maintain the capability to selectively disable Data Binding to provide an XML basedfragment suitable for use as input to alternative data binding technologies. Soap encoding supportUse of the soap encoding is essential deprecated in the Web Services Community, e.g ., the WS-I basic profile [8] excludes soap encoding. instead, literal usage is preferred, either in the RPC or document style. soap 1.1 encoding is supported in JAX-RPC 1.0 and 1.1 but its support in JAX-WS 2.0 runs counterto the goal of delegation of Data Binding to jaxb. therefore JAX-WS 2.0 will make support for soap1.1 encoding optional and defer description of it to JAX-RPC 1.1.support for the soap 1.2 encoding [4] is optional in soap 1.2 and JAX-WS 2.0 will not add supportfor soap 1.2 encoding. Backwards compatibility of generated artifactsJAX-RPC 1.0 and jaxb 1.0 bind XML to Java in different ways. generating source code that works with unmodified JAX-RPC 1.x client source code is not a goal. Support for Java versions prior to j2se 5.0JAX-WS 2.0 relies on collections of the Java language features added in j2se 5.0. It is not a goal to support JAX-WS 2.0 on Java versions prior to j2se 5.0. Service Registration and DiscoveryIt is not a goal of JAX-WS 2.0 to describe registration and discovery of services via UDDI or ebXML RR. This capability is provided independently by jaxr [16].

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.