Describes how to improve Java Web service performance

This article also demonstrates how to use the above three methods in your project and the scenarios that are appropriate for each method.

Web Services is a http://www.aliyun.com/zixun/aggregation/14107.html "> service-oriented architecture technology that provides services through standard WEB protocols to ensure that application services on different platforms can interoperate. Web Services (Web service) is a service based on XML and HTTP Communications, whose communication protocols are based primarily on SOAP, and service descriptions are discovered and obtained through WSDL, UDDI, and service metadata. This WEB service, based on XML standards and Internet protocols, is the next development direction of distributed computing, WEB services provide a bright prospect for communication and collaboration between business applications built from different resources, enabling them to collaborate with each other, without the impact of their underlying implementations.

JAX-RPC 1.0 is the original standard for Web services in Java, but because Jax-RPC 1.0 has a limited understanding of Web services functionality, Jax is born with 2.0 applications. The main goal of the Jax 2.0 development effort is to update the standards and successfully implement the industry's expectations for Jax-RPC 1.X. In addition, Jax 2.0 directly supports Xop/mtom, enhances the system attachment transfer ability and the system interoperability.

Analyzing the bottleneck of WEB service Energy by example

Through the above, it is not difficult to realize that WEB services, with its XML + HTTP loosely coupled, platform-independent features, are all spoiled and will become the basis for future data sharing. But at the same time we should realize that there are two sides to the world's contradictions: there are advantages, there will be shortcomings, WEB services are also so. Just as the performance of JAVA in its own way was fatal, WEB services also faced performance problems, as if "performance problems" were inherently "platform-independent" lingering enemies. But the problem has to be solved, practice is the only way to test and analyze the problem, let us first create a simple Web service to examine and analyze the implied performance problems.

Create a service

To create a service Java bean: First we create a bookstore service bean as simple as possible, and the service has only one qrybooksbyauthor, that is, according to the author (Author) the book under its name (list<book>).

Figure 1. Bookstore Service Bean (Bookstoresrvbean)

Entity classes for service input-authors (Author):

Figure 2. Author entity class (Author)

Entity classes that serve the output-book list:

Figure 3. Books entity Class (book)

Now that our service code has been completed, we are not here to discuss the business justification of this service, and the purpose of creating this service is simply to give an example as simple as possible to analyze the performance of the Web service.

The task below is to develop a Web service that is extremely cumbersome to write and publish compliant Web services, using IBM's Rational Software Architect (RSA) for the server side of the Web service and the development of the client.