This is the seventh article in the Java EE Web Services Development Series, which focuses on the use of various technologies or tools for Web service development under the j2ee1.3 platform in the previous topics in this series. Starting with this article, we will introduce the development of Web services under the j2ee1.4 platform.
This paper first introduces the architecture of Web services in j2ee1.4 platform, then introduces the newest specification and new technology of Web service in j2ee1.4 platform, then introduces the API for developing Web service and the development steps of Java-EE Web service, and finally introduces the development tool of Web service.
j2ee1.4 Web Services Architecture
The j2ee1.4 theme is Web Services, under the j2ee1.4 platform:
Allows the Java EE application component to be exposed to soap/http Web services;
Integrate with the original Web services;
Key Technologies for Web services: JAX-RPC;
Web service Framework under j2ee1.4: Web services for Java EE.
The new added technology for j2ee1.4 platform upgrades is mostly related to Web services. Under the j2ee1.4 platform, it becomes very convenient to develop, deploy, and discover Web services. Although the j2ee1.4 platform provides upgrades for Web services, the following:
Web Services is only a service channel in Java EE platform, so there is no need to change the architecture of Java EE, and the original Java EE component can be easily exposed to Web services;
The advantages of the Java EE platform still 訵 EB Service: scalability, reliability, openness.
The J2ee1.4web service architecture is shown in Figure 1.
In Figure 1, the gray represents the newly added technology in the j2ee1.4 platform, and the white represents the original technology. In the architecture diagram of Figure 1, the client of a Web service can be an applet or standard Java client, or a component running in a servlet or EJB container, and the client can access the Web service through Jax-RPC with the HTTP/SSL protocol. The service endpoint of a Web service runs in a servlet or EJB container, and it is Jax-RPC and Saaj as the operating environment.