No, it looks like I am going to have to write my own parser
implementation. I'll end up using the type conversions from the library
to make it a little easier on myself. I looked into extending
XmlRpcStreamTransport but it doesn't look like what I need.
All I basically need is to parse and serialize the messages. I'm
receiving them in a ByteBuffer and I have a specialized class that is
built from the parameters and method name (and thusly, needs to be
serialized back into xml).
I was looking into avoiding having to do this but I don't see any way to
get around starting up the built-in server.
-John Bellone
[EMAIL PROTECTED]
609.489.3112
Jochen Wiedmann wrote:
On Nov 8, 2007 4:47 PM, John Bellone <[EMAIL PROTECTED]> wrote:
I want to use the parser and XmlRpcRequest object without the overhead
of the server (already have one built - we're looking to keep the
transports separate from the networking). Right now I am thinking that I
am going to have to extend to the parser, but I don't see where it
returns an Object with parameters and a methodcall.
Sounds like a use case for subclassing the XmlRpcStreamTransport.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
