"It would be nice to have the xmlrpc endpoint configurable also."
What do you mean?  Currently, an xmlrpc user invokes the 'run' method with a
message parameter with the details of which class to use and the parameters
to pass.  By xmlrpc endpoint, do you mean 'run'?

As a second question, in Xindice 1.0, we had the 'db' name as the
handlerName (to use the terminology from
http://xml.apache.org/xmlrpc/server.html).  Why did we abandon that in favor
of this RPCMessageInterface being registered as the '$default'?  I'm not
particularly opposed to this change, but I can't seem to find where this was
discussed, and I don't intuitively understand why we redesigned the XMLRPC
interfaces in this way.

thanks
dave


-----Original Message-----
From: Kurt Ward [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 05, 2002 10:11 AM
To: [EMAIL PROTECTED]
Subject: Re: xml-rpc messages


> If I (as a Xindice user) want to add a new XMLRPC method to the server, I
> think I need to define a class inside the
> org.apache.xindice.server.rpc.messages domain, correct?  Personally, I'd
> like to see some way to create more domain specific methods. I don't
really
> want to add my personal classes to the 'official' xindice namespace, since
> they really have more to do with my application than with xindice.

Good point.  This could also be a replacement for XMLObjects instead of
digging it out of the 1.0 trunk and still allow users to extend the server
with stored procedure type messages.

> One possible solution would be for the RPCMessageInterface class to read a
> configuration file on startup which would map RPC method names to class
> names that service that method.  This is vaguely reminiscent of the Apache
> server's ability to map URIs to different handlers or shared objects.  I
> haven't thought about this a lot, but I like configuration files that
allow
> users (or administrators) to alter the "out of the box" behavior.  Does
that
> make sense?  If so, what do people think about  it?

It would be nice to have the xmlrpc endpoint configurable also.

Kurt


Reply via email to