Some of you (Daniel?) may remember a discussion I started a couple of
months back about changing the client classes to use the Commons
HttpClient. Well, I finally began work on it as I am working on a
project for which it would be useful. Of course as I get into it, I
want to make sure I hav
Hi,
I recently needed to add introspection support so a user could use one of the
C++ auto glue generation frameworks. I found an OLD set of patches for this,
but they were very out of date. Instead of using these, I kept the same
usage pattern but made a new implementation based on the curr
Hi,
Forgive me for being rather ignorant on introspection, but is there any
reason we want to require the XML-RPC server programmer to create public
static fields instead of using properties?
I do not speak for the rest of the list, so I can't answer your question
about whether we want that.
Hello,
I was wondering if there is any reason that XmlRpc.parse() throws a raw
Exception? (line 342, XmlRpc.java, CVS from today about an hour ago)
Why not create an IncompleteParserClassException or some such? Someone
give the go ahead and I will do it and submit a patch.
--ryan
I'm fine with properties, however the _public definitions are handy in one
regard: It is easy to mark methods that should be public inline in your
source file, rather than some sort of external file.
Any other opinions? I'm happy to go either way.
The introspection spec used to be on www.xm
