Hi,
We eagerly await a response to understand that the behavior we
experience is not unusual and we can consider this when we design and
develop our solution further.
In case there is a need to provide with an example to explain what we
mean, do let us know and we shall forward the same immediately.
Thanks and Regards,
Sajit
------------------------------------------------------------------------
------------------------------------------
-----Original Message-----
From: Sajit - SDTPL [mailto:sajit.dayanandan_at_stpdomain.com]
Sent: Saturday, April 14, 2007 4:43 PM
To: users_at_jax-ws.dev.java.net
Subject: stateful behavior of web service implementing Provider<Source>
Hi,
We are developing Web Services implementing Provider<Source>.
We notice that these Web Services maintains its state across service
requests. This was noticed when we realized that the constructor
associated to the class implementing this Web Service was being invoked
only once (whenever GlassFish is being started or at the time of Web
Service deployment). The constructor had code to initialize the fields
in this Class, some of which were also being populated from an SQL
database.
Is this behavior to maintain the state across multiple client service
requests correct (and as expected)? Can we assume that this would be
supported in the final / subsequent releases of JAX-WS. I would hasten
to add that this is a good feature to have for our application, as we
would be happy to avoid accessing the database for every request that is
being received by the Web Service :-).
I hope my query is clear and we look forward to your response.... In
case of trouble in understanding our concern, do let us know and we
shall respond with an example explaining the experience better.
Note that we are using GlassFish v2b41 and nightly build of JAX-WS 2.1.
Thanks and Regards,
Sajit
------------------------------------------------------------------------
------------------------------------------