LocalClientInvoker does not use any transport protocol for invoking
the ServerInvoker, instead will make call directly on it locally.
This increases performance since no serialization required as well
as needed for push callbacks where InvokerCallbackHandler is in
same JVM as the callback server.
- Tom Elrod
- $Revision: 3956 $
transport a request against a remote ServerInvoker
log.trace("Using local client invoker for invocation.");
log.trace("Error calling on " + serverInvoker + " because is in invalid state. Will retry with new server invoker.");
for(int x = 0; x < invokers.length; x++)
newServerInvoker = svrinvoker;
if(newServerInvoker != null)
"no local server to call upon.");
subclasses must provide this method to return true if their remote connection is connected and
false if disconnected. in some transports, such as SOAP, this method may always return true, since the
remote connectivity is done on demand and not kept persistent like other transports (such as socket-based
- boolean true if connected, false if not
connect to the remote invoker
disconnect from the remote invoker. Once disconnect called
will not be able to re-connect by calling connect since will
loose reference to server invoker.
This will set the local reference to the server invoker.
This is needed to so can make calls directly against server.
throw new RuntimeException("Can not set internal callback server port as configuration value (" + sPort + " is not a number.");
return new InvokerLocator(transport, host, port, "callback", metadata);