HTTP Session caching possible using WL7 JAX-RPC ?

Question

We're using WL7, and using the JAX-RPC API to access external webservices.
Basically, we create the appropriate 'stubs' from the target WSDL using
clientgen. Then we invoke the target method. Code looks something like this:
Client_Impl client = new Client_Impl; // implementation of target
ClientPort_Stub stub = client.getClientPort();
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, url)
stub.invoke(args);
Now, when is the actual endpoint URL being created ? Is it when the invoke()
method is called ?
It cannot be during the constructor since I pass the target URL after that ...
My problem is that I have to call the 'invoke' method quite frequently, and hence
would like the HTTP session to be reused, rather than recreated each time. Right
now,
I construct the stub each time I have to call the target method, and I'm wondering
if
I just cache the stub and keep calling the target method each time, will the underlying
HTTP session be reused ? Any ideas ?
Currently, if I do netstat on my Sun Solaris box (where this runs), I see the
TCP
connection being recreated during each invocation ...
-john

Answer 1

Hi John,
You can do multiple invokes on the same stub. There is no
need to create a new one for each invoke.
WLS 7.0 use HTTP 1.0 with keep alive. If the server respects
HTTP keep alive, then WLS will not create a new connection.
HTHs,
-manoj
"john" <[email protected]> wrote in message news:[email protected]..
>
We're using WL7, and using the JAX-RPC API to access external webservices.
Basically, we create the appropriate 'stubs' from the target WSDL using
clientgen. Then we invoke the target method. Code looks something likethis:
>
Client_Impl client = new Client_Impl; // implementation of target
ClientPort_Stub stub = client.getClientPort();
stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, url)
stub.invoke(args);
Now, when is the actual endpoint URL being created ? Is it when theinvoke()
method is called ?
It cannot be during the constructor since I pass the target URL after that...
My problem is that I have to call the 'invoke' method quite frequently,and hence
would like the HTTP session to be reused, rather than recreated each time.Right
now,
I construct the stub each time I have to call the target method, and I'mwondering
if
I just cache the stub and keep calling the target method each time, willthe underlying
HTTP session be reused ? Any ideas ?
Currently, if I do netstat on my Sun Solaris box (where this runs), I seethe
TCP
connection being recreated during each invocation ...
-john