Configuring the Context Path of the Asynchronous Response Endpoint
3.5.1.3 Configuring the Context Path of the Asynchronous Response Endpoint
When a client is running within a servlet or Web application-based Web service, it can use its ServletContext and context path to construct the asynchronous response endpoint. You pass the information as an argument to the AsyncClientTransportFeature, as follows: ■ When running inside a servlet: AsyncClientTransportFeature asyncFeature = new AsyncClientTransportFeaturegetServletContext; ■ When running inside a Web service or an EJB-based Web service: import com.sun.xml.ws.api.server.Container; ... Container c = ContainerResolver.getInstance.getContainer; ServletContext servletContext = c.getSPIServletContext.class; AsyncClientTransportFeature asyncFeature = new AsyncClientTransportFeatureservletContext; The specified context must be scoped within the current application or refer to an unused context; it cannot refer to a context that is scoped to another deployed application. The following tables summarizes the constructors that can be used to configure the context path of the asynchronous response endpoint. AsyncClientTransportFeaturejavax.xml.ws. wsaddressing.W3CEndpointReference replyTo , javax.xml.ws.wsaddressing.W3CEndpointRefe rence faultTo, boolean doPublish Configures the following: ■ Endpoint reference address for the outgoing ReplyTo and FaultTo headers. ■ Whether to publish the endpoint at the specified address. For more information, see Section 3.5.1.4, Publishing the Asynchronous Response Endpoint . AsyncClientTransportFeaturejavax.xml.ws. wsaddressing.W3CEndpointReference replyTo , javax.xml.ws.wsaddressing.W3CEndpointRefe rence faultTo, boolean doPublish, boolean useAsyncWithSyncInvoke Configures the following: ■ Endpoint reference address for the outgoing ReplyTo and FaultTo headers. ■ Whether to publish the endpoint at the specified address. For more information, see Section 3.5.1.4, Publishing the Asynchronous Response Endpoint . ■ Whether to enable asynchronous client transport for synchronous operations. For more information, see Section 3.5.1.5, Configuring Asynchronous Client Transport for Synchronous Operations . Note: When you use the empty constructor for AsyncClientTransportFeature, the Web services runtime attempts to discover the container in which the current feature was instantiated and publish the endpoint using any available container context. Table 3–6 Cont. Constructors for Configuring the ReplyTo and FaultTo Headers Constructor Description 3-14 Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server3.5.1.4 Publishing the Asynchronous Response Endpoint
Parts
» Oracle Fusion Middleware Online Documentation Library
» Roadmap for Developing Web Service Clients
» Roadmap for Developing Asynchronous Web Service Clients
» Overview of Asynchronous Web Service Invocation
» Steps to Invoke Web Services Asynchronously
» Configuring Your Servers for Asynchronous Web Service Invocation
» Building the Client Artifacts for Asynchronous Web Service Invocation
» Configuring the Address of the Asynchronous Response Endpoint
» Configuring the ReplyTo and FaultTo Headers of the Asynchronous Response Endpoint
» Configuring the Context Path of the Asynchronous Response Endpoint
» Developing the Asynchronous Handler Interface
» Propagating User-defined Request Context to the Response
» Creating the Web Service MakeConnection WS-Policy File Optional
» Programming the JWS File to Enable MakeConnection
» Using the JAX-WS Reference Implementation
» Propagating Request Context to the Response Monitoring Asynchronous Web Service Invocation
» Roadmap for Developing Reliable Web Service Clients
» Roadmap for Securing Reliable Web Services
» Overview of Web Services Reliable Messaging
» Steps to Create and Invoke a Reliable Web Service
» Configuring the Source and Destination WebLogic Server Instances
» Creating the Web Service Reliable Messaging WS-Policy File
» Programming Guidelines for the Reliable JWS File
» Configuring the Acknowledgement Interval
» Managing the Life Cycle of a Reliable Message Sequence
» Monitoring Web Services Reliable Messaging Grouping Messages into Business Units of Work Batching
» Overview of Web Service Persistence
» Roadmap for Configuring Web Service Persistence Configuring Web Service Persistence
» Using Web Service Persistence in a Cluster
» Cleaning Up Web Service Persistence Overview of Message Buffering Configuring Messaging Buffering
» Overview of Web Services Cluster Routing
» How Web Service Cluster Routing Works
» Monitoring Cluster Routing Performance Overview of Web Services Atomic Transactions
» Enabling Web Services Atomic Transactions on Web Service Clients
» Overview of Callbacks Steps to Program Callbacks
» Sending Binary Data Using MTOMXOP
» Streaming SOAP Attachments Oracle Fusion Middleware Online Documentation Library
» Additional Considerations When Specifying WSDL Location
» Disabling XML Catalogs in the Client Runtime Getting a Local Copy of XML Resources
» Overview of SOAP Message Handlers
» Designing the SOAP Message Handlers and Handler Chains
» Creating the SOAP Message Handler
» Configuring Handler Chains in the JWS File Creating the Handler Chain Configuration File
» Compiling and Rebuilding the Web Service
» Configuring the Client-side SOAP Message Handlers
» Overview of Web Service Provider-based Endpoints and Dispatch Clients
» Developing a Web Service Dispatch Client
» Registering a More Recent Version of the Jersey JAX-RS Shared Libraries
» Overview of RESTful Web Services Programming Web Services Using XML Over HTTP
» Overview of Stateful Web Services Accessing HTTP Session on the Server
» A Note About the JAX-WS RI Stateful Extension Overview of UDDI
» Description of Properties in the uddi.properties File
Show more