I'm wondering what the best approach is, when using v3.0 server-side, to dynamically select the receiving instance that implements remote methods. An example is creating a user-dependent handling instance of a class that implements a remote API.
I have something like this working in 2.0, where I extend 2.0's AuthenticatedXmlRpcHandler, use basic auth info to select a handling object (based on user id), then use an Invoker to execute the method of that object that implements the remote API. This approach has the advantage of leveraging the reflection-based dispatch, but on a per-user basis. It's not immediately clear to me what the best approach is to do something similar with the 3.0 class organization. The example of using AbstractReflectiveHandlerMapping.AuthenticationHandler on the website doesn't seem to accomodate this. Perhaps extending XmlRpcServerWorker or somesuch? Do others do something similar? An example, or any comments/suggestions would be most appreciated. Also, btw, a small detail on the website docs: The very last code example (of ServletWebServer) at http://ws.apache.org/xmlrpc/server.html has an extraneous line ClassLoader cl = Thread.currentThread().getContextClassLoader(); that isn't needed since it doesn't use PropertyHandlerMappings. Many thanks, Joshua -- View this message in context: http://www.nabble.com/Selecting-method-call-receiver-dynamically-in-v3.0-tf2228761.html#a6177060 Sent from the Apache Xml-RPC - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
