Here's what I was thinking initially for the XMLRPC configuration.
<xmlrpc encoding="utf8" driver="xerces">
<xmlrpc-server>
<handler name="$default"
class="org.apache.xindice.server.RPCDefaultMessage">
<method name="GetCollection"
class="org.apache.xindice.server.rpc.GetCollection" />
<method name="ListCollection"
class="org.apache.xindice.server.rpc.ListCollection" />
<method name="CreateCollection"
class="org.apache.xindice.server.rpc.CreateCollection"
/>
</handler>
</xmlrpc-server>
</xmlrpc>
My basic idea was to remove all hardcoded assumptions from the XMLRPC driver
code. I had initially thought to add this configuration information to the
system.xml file, but Vladimir make a good point that Xindice users who don't
use XMLRPC accessor wouldn't care about this information, and it would
simply clutter their config file.
But I think that some configuration along these lines would be extremely
simple to implement and provide the Xindice administrator complete control
over what XMLRPC methods are exposed and even allow him/her to add his/her
own methods without mucking inside the core of Xindice.
If this configuration sounds good, I'll make the changes ASAP since I really
would like to see a configurable xmlrpc server in 1.1. I don't know where
the configuration information should live, so if people think this config is
ok, I'd like to hear where they think it should live. Perhaps alongside
system.xml, there should be a drivers.xml or a xmlrpc.xml?
dave
-----Original Message-----
From: Vladimir R. Bossicard [mailto:[EMAIL PROTECTED]
Sent: Friday, January 03, 2003 7:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Release plans?
> Vladimir had started seriously documenting the end-user setup experience
> I believe. This is probably necessary (servlet stuff in particular) for
> this release, sothat people can actually install it :).
Since I was (indirectly) asked for my opinion, there it is:
I proposed a solution to end up the mess with the configuration of the
embed driver but the feedback I received doesn't IMO address the
problem. or maybe everyone thinks it's fine to use System.setProperty
to configure a driver.
I'm still interested to see how other external XMLRPC commands can be
handled by the xmlrpc driver. Someone proposed the Grep function but
noone came up with a solution to integrate it smoothly. Can someone
propose a solution? (since this has to do with the configuration, I will
not volunteer)
-Vladimir
--
Vladimir R. Bossicard
Apache Xindice - http://xml.apache.org/xindice
