Hi Alan, I looked at the sample. I may not understand it correctly, but what I want is not the handlers to access that extra information, but the server implementation itself. I mean the bindingimpl that was generated from WSDL. And there is no way that I can change the skeleton or the WSDL, because the generation is automated. But I can see that MessageContext has a static method getCurrentContext or something like that. This might be something similar to what I need. I'm wondering how can this be a static method, but hey, it might be MAGIC. :) Anybody can help me with this getCurrentContext ? What is this all about ? Can I really fetch the context for every incoming request, just like that ?
> I may be way off the point here but you might try taking a look at: > > samples/security/serversecuritydeploy.swdd > > I believe this is an example of using handlers configured via > the wsdd to > intercept the request on the server side. > > Good luck! > > alan > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, April 25, 2002 6:34 AM > > To: [EMAIL PROTECTED] > > Subject: RPC extra information > > > > > > Hi, > > > > > > I have only one question: > > I need to deploy a service. I'm generating skeleton > > classes, then deploying my own service. My problem is that > > I need to pass some extra information to my service, which > > is not described in the WSDL used to generate the skeleton. > > To be more specific: I have client sending some SOAP requests > > to my server, according to the WSDL. One of my server side handlers > > will add an extra parameter to the MessageContext, which will > > have to go all the way to the server. Is there any way to do this > > without modifying the WSDL before using WSDL2Java ? Maybe passing > > the whole messagcontext as a parameter to server function calls ? > > (and maybe even without rewriting the RPCProvider.java or any other > > existing Axis source) > > > > Regards, Geza > > >
