yeah yeah you are right glen, but my scenario is different from what you are referring to.
I want to know how to do this, if someone out there can help me :) On Tue, Nov 30, 2010 at 2:59 PM, Glen Mazza <[email protected]> wrote: > > Pardon the non-answer (hopefully someone else can answer this for you), but > generally you do not want to stupid-proof your web service calls in that > manner. If there is a problem with the Endpoint URL the SOAP client > developer is using it could be something more significantly wrong in his > coding--you'd be doing him a favor by returning an error than by silently > continuing to process the request, keeping him oblivious to the problem. > For example, if I'm accidentally appending username and cleartext passwords > to the endpoint URL, of course I would want your web service provider to > halt with a 404 or whatever error so I can be alerted to this major > problem. > > Redirections are OK for non-technical web surfers accessing browser web > pages, but that shouldn't be necessary with hardcoded SOAP clients built > off > a WSDL and programmed by developers. > > Glen > > > Manoel Farrugia wrote: > > > > As a web service I have a getGreeting() method which is accessed by: > > > http://localhost:8080/HelloWorldWebServices/services/HelloWorldPort/getGreeting > < > http://localhost:8080/HelloWorldWebServices/services/HelloWorldPort/getGreeting1?arg0=Manoel > > > > > > Now I want that any other request method which does not exist in my web > > service (for example getGreetingMe()) is redirected to getGreeting() as > > the > > address above. > > > > How should I tackle this idea? > > > > Thanks > > Manoel > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Interceptors-How-to-handle-an-unknown-request-tp3285864p3286099.html > Sent from the cxf-user mailing list archive at Nabble.com. >
