Configuring individual Axis Services

[Chaudhri Rohit-CRC037 <Ro...@motorola.com>]

Hello,
Just found out from reading a posting on the List that it is possible to
access the ServletContext from a Service (either by the
javax.xml.rpc.server.ServiceLifeCycle or the
org.apache.axis.MessageContext). A ServletContext can be used(among other
things) to hold global context-wide initilization/configuration parameters.
Is there a standard way to some how configure web services individually? I
mean, how/where to store initilization/configuration information specific to
individual Web Services & how would they be available to the Web Services at
runtime.

Thanks
Rohit

Re: Configuring individual Axis Services

[Steve Loughran <st...@iseran.com>]

----- Original Message -----
From: "Chaudhri Rohit-CRC037" <Ro...@motorola.com>
To: <ax...@xml.apache.org>
Sent: Friday, August 23, 2002 8:34 AM
Subject: Configuring individual Axis Services


> Hello,
> Just found out from reading a posting on the List that it is possible to
> access the ServletContext from a Service (either by the
> javax.xml.rpc.server.ServiceLifeCycle or the
> org.apache.axis.MessageContext). A ServletContext can be used(among other
> things) to hold global context-wide initilization/configuration
parameters.
> Is there a standard way to some how configure web services individually? I
> mean, how/where to store initilization/configuration information specific
to
> individual Web Services & how would they be available to the Web Services
at
> runtime.

There are big changes to how axis is configured going underway in CVS; the
key point being that web.xml based config is often a bad way to configure
stuff, when things like JNDI based directories are better. So have a look at
todays code to see what the latest configuration mechanism is.