Use message level security

 Use fine-grained Web services

 Use document/literal instead of RPC/encoded

 Avoid stale data in the UDDI registry by turning off caching

 Expanding the reach of your company information.

 Providing transactional services such as credit card payment processing.

 Making existing services available to a business process to orchestrate services.

 Enabling interoperability between heterogeneous services to create time-critical solutions.

 To provide message level security

 To allow integration with Web 2.0 applications

 To be able to use XML to format response messages

 To be able to use the HTTP or HTTPS transport protocols

 Set the faultCode value to soap：Transaction

 Include a Fault element in the SOAP message

 Include a mustUnderstand attribute in the header entry

 Include a detail element containing application-specific elements according to the XML Schema

 SAAJ V1.2

 JAX-RPC V1.0

 WS-Coordination

 WS-I Basic Profile （BP） V1.1

 Managed persistent

 Managed non-persistent

 Unmanaged non-persistent

 Managed persistent and Transaction （enableTransactionalOneWay）

 Managed non-persistent and Transaction （enableTransactionalOneWay）

 Unmanaged non-persistent and Transaction （enableTransactionalOneWay）

 RPC/literal

 RPC/encoded

 Document/encoded

 Document/literal

 Document/literal wrapped

 The ObjectFactory class is the generated Service Endpoint Interface class

 The ObjectFactory class is the generated service provider class that is used by the JAX-WS client.

 The ObjectFactory class takes the targetNamespace value and creates the directory structure.

 The ObjectFactory class allows you to programatically construct new instances of the Java representation for XML content.

 To integrate legacy systems

 To propagate security context

 To expose fine grained operations

 To use with process choreography

 For B2B （business to business） applications