You could implement access control via a handler (extend org.apache.axis.handlers.BasicHandler for instance), that way the code controlling access to your service won't be mixed with the service itself; multiple services can share the same handler, etc.
However, as others have pointed out, undeploying the service might be a better solution for what you're trying to do. > -----Original Message----- > From: Miller, Janet [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 04, 2004 2:52 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: Newbie: Disabling a Web Service > > This is a good solution to be implemented in code that I > could definitely do pretty easily. > > I guess there's no easier way to just disable the service > using some kind of Axis command or something? > > -----Original Message----- > From: James Black [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 04, 2004 2:49 PM > To: [EMAIL PROTECTED] > Subject: Re: Newbie: Disabling a Web Service > > > Miller, Janet wrote: > > >I want to disable the web service programatically, so I don't think > >Undeploying would be the best option. Is there any other way to do > >This? > > > > > It would need to be password protected, but you could have a static > variable that your webservice uses, where if it is true, then process > the request, if false, then return an exception or an empty result. > > Then you would have added one function to your webservice that will > set this variable to true or false. > > -- > "Love is mutual self-giving that ends in self-recovery." Fulton Sheen > James Black [EMAIL PROTECTED] > >
