Jochen Wiedmann (JIRA) wrote:
Walter, are you interested in getting this into the 3.0 branch?
I am, but first I have a few issues with the 3.0 branch that I don't
like. First and foremost, the capabiliry to expose the methods on
particular instances of a class has been removed and replaced with a
default-constructor/proerty-file-based API that would be much less
convenient for me to use.
Specifically, the simple "ws.addHandler(name, someRandomObject)"
mechanism is _very_ handy, and going out to property files is, for my
purposes (rapid prototyping and integration of code in different
languages) vastly less convenient. Therefore, before I have any
interest in workin on the 3.0 branch, you'll have to agree to reinstate
the older option of providing arbitrary Object instances at runtime to a
handler mapping.
I don't care if the call structure changes to
((PropertyHandlerMapping)ws.getXmlRpcServer().getHandlerMapping()).addHandler(name,
obj);
if that would be preferred, and I will whip up a quick patch to add such
a call if you like.
- First of all, you should propose necessary extensions for the interfaces
handlermapping and handler.
(Recommended: Create an interface like XmlRpcMetaDataHandlerMapping, which
extends
XmlRpcHandlerMapping.)
- Second: Make the existing classes implement your new interfaces.
- Third: Provide special handlers, which provide the requested metadata.
Can do, given the conditions above.
