Examples of invokeOneway()

• com.arjuna.webservices.SoapClient.invokeOneWay()
  Invoke a one way request on a service. @param request The request object. @param url The destination URL. @throws SoapFault For errors processing the request. @throws IOException for processing errors.
• javax.xml.rpc.Call.invokeOneWay()
  Invokes a remote method using the one-way interaction mode. The client thread does not block waiting for the completion of the server processing for this remote method invocation. This method must not throw any remote exceptions. This method may throw a JAXRPCException during the processing of the one-way remote call. @param inputParams Object[]--Parameters for this invocation. Thisincludes only the input params. @param params @throws JAXRPCException if there is an error in theconfiguration of the Call object (example: a non-void return type has been incorrectly specified for the one-way call) or if there is any error during the invocation of the one-way remote call
• javax.xml.ws.Dispatch.invokeOneWay()
  Invokes a service operation using the one-way interaction mode. The operation invocation is logically non-blocking, subject to the capabilities of the underlying protocol, no results are returned. When the protocol in use is SOAP/HTTP, this method MUST block until an HTTP response code has been received or an error occurs.

  The client is responsible for ensuring that the msg object when marshalled is formed according to the requirements of the protocol binding in use. @param msg An object that will form the message or payload ofthe message used to invoke the operation. @throws WebServiceException If there is any error in the configuration ofthe Dispatch instance or if an error occurs during the invocation.

• org.apache.axis.client.Call.invokeOneWay()
  Invokes the operation associated with this Call object using the passed in parameters as the arguments to the method. This will return immediately rather than waiting for the server to complete its processing. NOTE: the return immediately part isn't implemented yet @param params Array of parameters to invoke the Web Service with @throws JAXRPCException is there's an error
• org.apache.axis2.jaxws.core.controller.AxisInvocationController.invokeOneWay()
  Note to developer: When making a change or fix to this method, please consider all 5 Proxy/Dispatch "invoke" methods now available in JAX-WS. For Dispatch, these are: 1) Synchronous invoke() 2) invokeOneWay() 3) invokeAsynch (Future) 4) invokeAsynch (Callback) For Proxy: 5) invokeSEIMethod()
• org.apache.axis2.jaxws.core.controller.InvocationController.invokeOneWay()
  Performs a one-way invocation of the client. This is SHOULD NOT be a robust invocation, so any fault that occurs during the processing of the request will not be returned to the client. Errors returned to the client are problems that occurred during the sending of the message to the server. @param ic
• org.apache.axis2.jaxws.server.dispatcher.EndpointDispatcher.invokeOneWay()
• org.jboss.remoting.Client.invokeOneway()
  Will invoke a oneway call to server without a return object. This should be used when not expecting a return value from the server and wish to achieve higher performance, since the client will not wait for a return. This is done one of two ways. The first is to pass true as the clientSide param. This will cause the execution of the remote call to be excuted in a new thread on the client side and will return the calling thread before making call to server side.

  The second, is to pass false as the clientSide param. This will allow the current calling thread to make the call to the remote server, at which point, the server side processing of the thread will be executed on the remote server in a new executing thread.

  NOTE: The treatment of server side oneway invocations may vary with the transport. The client side transport is not required to wait for a reply from the server.

• org.objectweb.celtix.transports.ClientTransport.invokeOneway()
  invoke on a oneway operation on a remote service. @param context