Did you use the wizard to craete a Java Bean skeleton? On the "Web Service Skeleton Java Bean Configuration" page, for "Service deploy Scope" specify "Application" rather than the default value of "default".
The resulting entry in the generated file "ibm-webservices-bnd.xmi" for the scopt attribute might look similar to the following:
<wsdescBindings xmi:id="WSDescBinding_1219844169757" wsDescNameLink="myDescName"> <pcBindings xmi:id="PCBinding_1219844169757" pcNameLink="myLinkName" scope="Application"/></wsdescBindings>
This should use a singleton (Application scoped) rather than a request scoped bean. Hope that helps.
Mike
----- Original Message ----
From: Mike Burdette <Mike.Burdette@xxxxxxxxxxxxx>
To: java400-l@xxxxxxxxxxxx
Sent: Monday, 17 November, 2008 13:30:36
Subject: Object creation as pertains to Web Services in Websphere...
Hi:
We are developing a Java based web service in Rational 6.0.1 to be
deployed in WAS 6.0. The web service is being used by a .Net front end to
fetch as well as update data on the iSeries.
We notice that when deployed to WAS 6.0 on the iSeries, the constructor
for the Java object that provides the Web Service is called each time the
web service is called. We would like to provide some initialization
instructions that would persist between calls to the web service, but it
slows our response when the object is created for each request. (The
object is created only once when using the Websphere Test Environment.)
Any thoughts on how to do this?
Thanks
midrange.com
