Daniel Janus wrote:
mapping.load(Thread.currentThread().getContextClassLoader(), url);
That sounds like a problem, which we should not simply handle by
changing the FAQ. Would you please be so kind to create a JIRA issue,
where we can continue the discussion?
I've created issue XMLRPC-147:
https://issues.apache.org/jira/browse/XMLRPC-147
I really can't believe that the multiple layers of hackery outlined in
the FAQ are needed to get what *should* be a fairly straightforward and
regularly-used bit of information - the client's address. And to add
insult to injury, it appears that the entry in the FAQ is *still* wrong
5 months after this was reported. Quite frankly, the API is an abysmal
mess - having to subclass implementation classes such as
XmlRpcHttpRequestConfigImpl is a pretty clear indication that the whole
thing is badly designed, and as for class names like
RequestProcessorFactoryFactory.RequestSpecificProcessorFactoryFactory,
if it wasn't in the docs I'd think it was someone trying to have a laugh.
--
Alan Burlison
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
