This chapter provides a summary table advanced features for software developers who program WebLogic Web services using Java API for XML Web Services (JAX-WS).
Table 1-1 Programming Advanced Features Using JAX-WS
| Advanced Features | Description |
|---|---|
|
Describes how to use Web Services Addressing (WS-Addressing) to address Web services and their associated messages in a transport-neutral way. |
|
|
Review best practices for developing Web service clients. |
|
|
Invoke a Web service asynchronously. |
|
|
Chapter 5, "Roadmap for Developing Reliable Web Services and Clients" |
Review best practices for developing asynchronous and reliable applications together. |
|
Use Web service reliable messaging to enable an application running on one application server to reliably invoke a Web service running on another application server, assuming that both servers implement the WS-ReliableMessaging specification. |
|
|
Manage persistence for Web services. Web service persistence is used by advanced features to support long running requests and to survive server restarts. |
|
|
Configure message buffering for Web services. |
|
|
Review best practices for using Web services in a cluster. |
|
|
Use Web services atomic transactions to enable interoperability with other external transaction processing systems. |
|
|
Publish a Web service endpoint at runtime, without deploying the Web service. |
|
|
Notify a client of a Web service that an event has happened by programming a callback. |
|
|
Send binary data using MTOM/XOP and/or streaming SOAP attachments to optimize transmission of binary data. |
|
|
Invoke a Web service based on a service endpoint interface (SEI) dynamically at run-time without using |
|
|
Use XML catalogs to resolve network resources to versions that are stored locally. |
|
|
Handle SOAP faults and exceptions. |
|
|
Create and configure SOAP message handlers for a Web service. |
|
|
Develop Web service provider-based endpoints and dispatch clients to operate at the XML message level. |
|
|
Program Web services using XML over HTTP. |
|
|
Chapter 21, "Programming Stateful JAX-WS Web Services Using HTTP Session" |
Create a Web service that maintains state between service calls. |
|
Appendix A, "Pre-packaged WS-Policy Files for Web Services Reliable Messaging and Make Connection" |
Review the pre-packaged WS-Policy files that contain typical reliable messaging assertions that you can use to support reliable messaging. |
|
Appendix B, "Example Client Wrapper Class for Batching Reliable Messages" |
Provides an example client wrapper class that can be used for batching reliable messaging. |
Note:
The JAX-WS implementation in Oracle WebLogic Server is extended from the JAX-WS Reference Implementation (RI) developed by the Glassfish Community (see https://jax-ws.dev.java.net/). All features defined in the JAX-WS specification (JSR-224) are fully supported by Oracle WebLogic Server.
The JAX-WS RI also contains a variety of extensions, provided by Glassfish contributors. Unless specifically documented, JAX-WS RI extensions are not supported for use in Oracle WebLogic Server.
For an overview of WebLogic Web services, standards, samples, and related documentation, see Introducing Web Services.
JAX-WS supports Web Services Security (WS-Security) 1.1. For information about WebLogic Web service security, see Securing WebLogic Web Services for Oracle WebLogic Server.