The development means of webservice

first, the development means of WebService
At present, there are 2 kinds of development methods about WebService
1, JDK development (JDK must be 1.6 and later, because the JDK was introduced in the 1.6 version and Support webservice development);
2, the use of WebService framework development, the current popular WebService framework is known to have the following: Apache Axis1, Apache Axis2, Codehaus XFire (XFire mode), Apache CXF, The more common is the Apache CXF way.
Second,introduction of WebService development Framework

(Here is an excerpt from others, the full text please see HTTP://BLOG.CSDN.NET/THUNDER4393/ARTICLE/DETAILS/5787121)
2.1 Apache Axis1
Axis is essentially a soap engine (Apache Axis is a implementation of the soap), providing the basic framework for creating server-side, client-end, and gateway SOAP operations. But axis is not exactly a soap engine, it also includes:
L is a stand-alone SOAP server.
L is a server that embeds a servlet engine (such as Tomcat).
L Support WSDL.
L provide tools to convert WSDL into Java class.
L provide an example program.
L provides TCP/IP packet monitoring tools.
2.2 Apache Axis2
Apache Axis2 is more efficient, more modular and more XML-oriented than Apache AXIS1, enabling easy plugin modules to extend new features and features, such as security and reliability. Apache Axis2 is based on Apache AXIOM, which is a high performance, pull-based XML object model. Key features of Apache Axis2:
L Parse XML faster. Use your own object model and Stax (streaming API for XML).
l Lower memory consumption.
L Support Hot deployment. New services are added to the system without restarting the service.
L Support Asynchronous WebService,
L MEP support, flexible support for message Exchange Patterns defined in WSDL 2.0 (MEPs)
L more flexible. The engine provides developers with ample freedom to expand customer header information processing, System management,
L more stability.
The transport framework does not rely on specific protocols. For integration and transport protocols (SMTP, FTP, message-oriented middleware, etc) there is a simple and abstract, engine core is completely independent of the specific transport protocol.
L Support WSDL. Support WSDL1.1, WSDL2.0.
L Easy integration of other components (add-ons). Several Web services have been integrated, including: wss4j for Security (Apache Rampart), Sandesha for reliable messaging, kandula which are an Encapsula tion of ws-coordination, ws-atomictransaction and ws-businessactivity.
L Good Extensibility.
2.3 Codehaus XFire
The Xfire core is a lightweight, Stax-based message processing model that interacts with SOAP messages, supporting different types of binding mechanisms, containers, and transport protocols.
Supports WebService standards-SOAP, WSDL, WS-I Basic profile, ws-addressing, ws-security, etc.
L High Performance Soap STACK
L Pluggable Bindings POJOs, XMLBeans, JAXB 1.1, JAXB 2.0, and Castor support
L Use the JSR 181 API Configuration service through Java1.5 and 1.4 (Commons attributes JSR Syntax 181)
L support multi-medium Transfer Protocol-HTTP, JMS, XMPP, IN-JVM, etc.
L Embeddable and Intuitive APIs
L support Spring, Pico, Plexus, and loom
L Support JBI
L Client and server stub code generation
L Support JAX-ws Early Access
2.4 Apache CXF
Apache CXF is an open source service framework. CXF can be used in front-end programming APIs development services, such as: Jax-ws and Jax-rs, the main features include:
L Support Web services standards. Includes: SOAP, the WSI Basic profile, WSDL, ws-addressing, Ws-policy, ws-reliablemessaging, ws-security, ws-secureconversation and Ws-securitypolicy.
L support different types of front-end development models. CXF implements JAX-WS APIs to support JAX-RS development.
L easy to use. CXF design is simple and intuitive, with simple APIs to quickly build code-based services, MAVEN plug-ins make tool integration easier, JAX-WS API support, and Spring 2.x XML make configuration easier.
L support binary and legacy protocols. CXF is designed as a pluggable architecture that supports not only XML but also non-XML type bindings, such as JSON and CORBA, in combination with different transport protocols.
Performance comparison of several popular webservice frames http://blog.csdn.net/thunder4393/article/details/5787121

The development means of webservice