I overlooked the reference to direct use of RPC::XML::Parser in the POD
for RPC::XML. I will address this with two fixes: (1) Correct the
documentation to refer to RPC::XML::ParserFactory, and (2) Make the
constructor for RPC::XML::Parser handle a special-case that hands off to
the factory constructor.
If I cannot finish the other changes scheduled for 0.70 in a reasonable
span of time, I will release a 0.691. To be honest, I didn't know anyone
was using the parser class directly like this, and I worried only about
keeping the interface to the client and server classes consistent. I
apologize for this.
As an interim fix, if you replace RPC::XML::Parser with
RPC::XML::ParserFactory in the Catalyst class, it should work. However,
that would require making that package dependent specifically on the
0.69 version of this module. See the documentation for RPC::XML::Parser
and RPC::XML::ParserFactory in the 0.69 distribution.
(Note that due to an oversight on my part, the RPC::XML::ParserFactory
documentation refers to an option based on XML::LibXML, which was not
ready for the 0.69 version. The references to it should have been
removed, as currently only the XML::Parser implementation is available.)
--
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Randy J. Ray Silicon Valley Scale Modelers:
http://www.svsm.org
rjray@blackperl.com
randy.j.ray@gmail.com
