Looks like this is transport specific(http). Does'nt work for me. I am using Tibco messaging middleware as the transport. Any idea how I can make this work ?

Srikant

Russell Butek wrote:
You're using DII?  Then you have an org.apache.axis.client.Call object:
Call.setMaintainSession(true);

Or if you want to strictly follow JAX-RPC (you have a javax.xml.rpc.Call
object and don't want to cast to org.apache.axis.client.Call):
Call.setProperty("javax.xml.rpc.http.session.maintain", new Boolean(true));

Russell Butek
[EMAIL PROTECTED]


Ramaswamy Srikant <[EMAIL PROTECTED]> on 02/14/2002 11:41:59 AM

Please respond to [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
cc:
Subject: Re: service ins! tances



How do I set this option if I am not using WSDL2Java ?


Srikant

Jean Marc Taillant wrote:

Hi,
Try to use scope="Application" instead of scope="session".
To set this option use -d in WSDL2Java

Hope this help us

Jean Marc

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 14, 2002 3:31 PM
Subject: service instances

Hello,

I've just created and deployed a simple web service using Axis.

Each time I call the web service, a new instance of the class
implementing my web service is created.

Is there any way of controlling this behaviour ? I mean, is it possible
to have one instance per request (current behaviour), or one instance
per
server, a pool of instances ...

My web service needs to access a database. So, I would like to maintain
a persistent connection to the database. I could use a singleton or
a static member but it would take some time when processing the first
request. Is is possible to tell Axis to pre-load some classes when it
starts up to avoid latency with the first request ?

Thank you for your help,

Tom.





Reply via email to