"WebService" chapter III, Sebservice related technologies and client calls

This chapter provides a general overview of WebService technologies and client-side invocation techniques.

The figure above contains almost all the relevant content of the current webservice. I'm going to go through two big chunks to illustrate, that's the service side, the client.

The service side mainly introduces the following 3 kinds:

1. Axis1 or Axis2 release WebService.

2. Use Xfire to publish WebService.

3. Use the latest CXF to publish WebService.

the deployment of a service-side is primarily guided by the following steps:

1. Add jar packs and introduce relevant technologies to provide basic capabilities for publishing services.

2. Create a new XML file to control which methods need to be published and which methods are not.

2. Modify the Web.xml file to add a servlet access path. This is provided by axis, XFire, and cxf that automatically generates a WSDL for you.

Thing So we can access the service and call the.

The method of client invocation is mainly described as follows:

1. Wsimport Technology.

2. Use the API interface provided by axis or Xfire or CXF.

3. HTTP POST method (almost no one uses this).

4. HTTP Get Way (almost no one uses this).

5. SOAPUI Software Test call.

6. MyEclipse Integrated WebService browser invocation.

At present, WebService is almost as much as listed above, the content of the future in accordance with this outline 1.1 points to write. On various

The difference between technology and I did not study very carefully. But the company is using CXF,CXF as if it were a newer technology.

At the beginning it was axis, which developed a xfire. Then Xfire based on adding something to the cxf. Between them.

All kinds of secret concern on Baidu look for it.