| Invalid XML [message #257635] |
Tue, 09 October 2007 04:14 |
Eclipse User |
|
|
|
We have a small tool which converts an unrelated report design format to
a BIRT report design and we noticed, while debugging it, that neither
the RCP Designer nor the full-blown Eclipse BIRT Designer are very
helpful in isolating where problems lie.
They both seem to simply give up the ghost and state "Oi, go fix the
problem in your report design then come back and see me" (I'm
paraphrasing, of course).
Has anyone else figured out a way to find where problems lie in the XML?
Two of the examples spring immediately to mind:
1/ We generated the string "select column from table where column <>
value" in the SQL statements and the designer choked (rightly so)
because it thought the "<" character was the beginning of an XML tag.
Changing it to "<>" fixed that one.
2/ The data transfer utility which transferred the file from platform to
platform insisted on adding a CTRL-Z to the end of the file (following
the closing </report> tag). Removing the character fixed it.
In both these cases, it would have been nice if the designer had told us
exactly what the problem was (such "You have a naked '<' character in
your SQL on line N" or "WTF is that CTRL-Z doing at the end of the
file?") or at least gave us the position in the file where it choked so
we wouldn't have to analyse the entire thing.
Maybe I'm missing something and there IS a means to do this. In that
case, I'm open for educating from the masses.
Cheers,
Pax.
|
|
|
Powered by
FUDForum. Page generated in 0.05631 seconds
Home