The error message that you cite talks about input XML not being well-formed, why do you look for a solution that can handle bigger XML-files? | [reply] |
I suspect the real problem is hinted at in the (invalid token) [. . . (blah blah) . . ] line. More specifically in the (bla bla) part, which should contain some indication as to where in the XML the error occurs.
update: or just save the XML somewhere and run it through some other conforming parser to see what's up.
| [reply] [d/l] [select] |
Solved the problem. Used XML::RPC module instead of Frontier::Client. No troubles after that.
Thanks for the help. | [reply] |
| [reply] |
The reason that I assumed that the error was related more to memory limitations was the pattern that it seemed to follow. Although there seems to be a problem with quick, successive queries, the error is also given after very general queries with large result sets such as "person" and "live."
Concerning Joost's comment, the line, column, byte triplet of the error are dependent upon the query. For example, the error returned for "person" is ". . . (invalid token) at line 1449, column 38, byte 61239 at C:/Perl/lib/XML/Parser.pm line 187," while a query for "live" returns ". . . at line 516, column 31, byte 22317 at C:/Perl/lib/XML/Parser.pm line 187." What may be more useful is that the error occurs on line 187 of the XML::Parser module.
Is it more likely that what I've thought to be a memory error has more to do with the data sent from the XML-RPC server itself? If this is the case, would the implementation of XML::Smart within Frontier::Client solve the problem? | [reply] |