Cxf weather forecast

First, the client ends with a WSDL from the server to the WebService, and declares a proxy class at the client.

This proxy class is responsible for the requests and responses of the WebService server.

When a data (in XML format) is encapsulated into a data stream in SOAP format and sent to the server, it will generate a process object and parse the received SOAP packet, and then process this thing, and then SOAP encapsulates the processed calculation result, and then send this packet as a response to the client's proxy class. Similarly, this proxy class will parse SOAP packets and then perform subsequent operations. This is the running process of a WebService.

Web services are roughly divided into five levels:

1.Http transport channel

2.XML data format

3.SOAP encapsulation format

4. Description of 4.WSDL

5.UDDI

2、RCP

The internal operation of RPC call from client to server is roughly as follows:

1. Call the client handle; Execution transmission parameters,

2. Call the local system kernel to send network messages,

3. The message is transmitted to the remote host.

4. The server handle gets the message and gets the parameters.

5. Execute the remote program,

6. The executed procedure returns the result to the server handle.

7. The server handle returns the result and calls the remote system kernel.

8. The message is returned to the local host,

9. The kernel receives the client handle.

10. The client receives the data returned by the handle.

The difference between 3.webservices/corba/jms/rpc/rmi.

The service provided by the web service is based on the web container, and the bottom layer uses/view/72cc476b561252d380eb6e22.html, while the RMI object is bound in the local JVM and only passes function parameters and return values through the network (it is a request response mechanism).

3.4CORBA、RMI、webservices

In the system communication architecture using CORBA, CORBA uses a unified IDL interface, and webservices use wsdl. One is c/s naming service, and the other is web-based service. CORBA also has an event service, which is a service on the naming service and can realize message notification, while webservices is a request-response mode. Corba has been mature for a long time, supported by many big companies, and then gradually declined. Using CORBA is a very complicated matter. For the later system, it is recommended to use webservices for development. Now eclipse provides good support for the rapid development of webservices servers, and supports Axis, axis2, Xfire and cxf. Please refer to their comparison.

The idea of enterprise SOA architecture is a good entrance to enterprise ESB system.

CORBA is a distributed interoperability standard proposed by OMG organization in the early 1990s, and JACORB supports cross-platform language Java. RMI directly embeds the distributed object model into the Java language, so that Java programmers can write distributed programs naturally, without leaving the Java environment, and without involving CORBA IDL and the transformation from Java to CORBA type. However, RMI does not conform to CORBA standard, and it is basically a Java-to-Java technology, so it is difficult to achieve interoperability with objects written in other languages.

RMI and CORBA are often regarded as competing technologies because they both provide transparent access to remote distributed objects. But these two technologies are actually complementary, and the advantages of one can just make up for the disadvantages of the other. The combination of RMI and CORBA produces RMI-IIOP, which is the basis of enterprise server-side Java development.

1997, IBM and Sun Microsystems launched a cooperation plan to promote the development of Java as an enterprise development technology. The two companies pay special attention to how to use Java as a server-side language to generate enterprise-level code that can be integrated into existing architectures. What is needed is a remote transmission technology, which has both RMI of Java.

(Remote Method Call) has less resource occupation and more mature robustness of CORBA (Common Object Request Broker Architecture) technology. Due to this demand, RMI-IIOP came into being, which helped push the Java language to the leading position of the mainstream language developed by server-side enterprises.