Hello,
Thanks for the response.
I studied the code a little more after reading that email. I have
another idea on doing it and I would appreciate an analysis of that.
I was thinking of extending a Server class like XmlRpcServletServer
and then overloading the function newConfig which returns a new class
MyConfig which is a subclass of XmlRpcHttpRequestConfigImpl. Now before
calling doPost in servlet I can set the required parameters in MyConfig
and they will show up in execute method of the handler.
I would appreciate any comments on this.
Thanks a lot,
Raghbir Singh
Jochen Wiedmann said the following on 09/20/07 02:03:
On 9/20/07, Raghbir Singh <[EMAIL PROTECTED]> wrote:
I have been using XML-RPC version 2 for some time and I decided to
upgrade to version 3 but I am stuck at a roadblock which comes from
XmlRpcContext.
My server used one handler and that handler extended
ContextXmlRpcHandler and for every request I created an object of a
class that implemented the XmlRpcContext interface. This way I could
pass extra per-request information to the server like which database
connection to use etc.
Since there is not ContextXmlRpcHandler and XmlRpcContext in version
3, can anybody tell me how to do this now ?
The suggested way to do this is to subclass
RequestSpecificProcessorFactoryFactory and let it configure your
processor objects.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
