Make it possible to access and change web service options on client side
The current implementation of the client-side of the web services lacks a way to access specific configuration options. This may be needed to avoid problems with local network setup, proxies, etc. There are a lot of possible options in the Axis API so we need this functionality to be as open as possible.
To be specific the
AbstractRPCClient.getService() method creates an Axis object on which users may want to call
getOptions() to change some of the default options. With the current BASE API the only workaround that doesn't involve changing the BASE code is to subclass all
AbstractRPCClient subclasses and override the
getService() method. This is not very elegent since there are several such classes and the new
getService() will be added to each one of them.
A better approach may be to create a
ServiceFactory interface which has a
createService() method. The default implementation would then work as the
AbstractRPCClient.getService() does today. The last step is to figure out a way to switch to another
ServiceFactory implementation either by having a configuration file or by being able to specify it programmatically.
More information about a specific problem can be found in the mailing list archive: http://email@example.com/msg00309.html
Change History (6)
comment:1 by , 16 years ago
|Make it possible to access and change web service options → Make it possible to access and change web service options on client side