- Original Message -
From: "John Wilson"
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 28, 2002 7:29 PM
> The exception does not come from the parser. It comes from XmlRPC.java.
You're right of course; it's been a long day, and the words "MiniML" just
leapt out at me. How could I ever h
- Original Message -
From: "Phil Wilson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 28, 2002 7:23 PM
Subject: Re: Empty return value
> > can you post the error you get?
>
> Sure thing,
>
> Here's what I get
>
> startElement: dateTime.iso8601
> endElement: dateTime
> can you post the error you get?
Sure thing,
Here's what I get
startElement: dateTime.iso8601
endElement: dateTime.iso8601
java.lang.RuntimeException: Unparseable date: ""
at org.apache.xmlrpc.XmlRpc$Value.characterData(XmlRpc.java:597)
at org.apache.xmlrpc.XmlRpc.endElement(XmlRpc.java:388)
Paul Libbrecht <[EMAIL PROTECTED]> writes:
> A much more dirty approach may also be to use ThreadLocals... never
> worked with them.
Catalina's and Turbine's Pipelines have a good example of them. They
work well.
- Dan
- Original Message -
From: "Phil Wilson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 28, 2002 3:42 PM
Subject: Empty return value
> Hi,
>
> Part of the return from an XML-RPC call I make is an empty field
> ( in fact), but the
> included MiniML parser chokes on thi
Hi,
Part of the return from an XML-RPC call I make is an empty field
( in fact), but the
included MiniML parser chokes on this (unparseable date: "").
As far as I'm aware, an empty element is valid XML, so shouldn't this be
dealt with?
Thanks,
Phil
Well, the sad thing is that there has been so many changes that my
attempts to merge my existing distribution and the cvs checkout of today
produced much too many differences, most of which are due to
re-indenting... one file had 121 differences...
I think I can only give up.
As far as I under
You surely can filter the hosts (see the setParanoid method of
WebServer) but indeed, there is nothing possible with the very developer
friendly approach.
An easy extension might be to have another interface than the
XmlRpcHandler handler interface where the execute(String method, Vector
para
