Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1650 XML: some errors go to stdout instead of errorlist

closed-fixed
Eric Le Lay
None
5
2012-09-20
2012-09-10
Alan Ezust
No

I just created a new XML file, and I had :xml.root=index.xml:
at the top, which is where my schema info is, etc.

I forgot to add a <xi:include href="myNewFile.xml" /> in my root document though.

And I started typing stuff. Completion worked great. But if I had a parse error,
such as a missing close-tag, I would see the error in standard output instead of errorlist.

9:26:47 AM [SwingWorker-pool-1-thread-33] [error] SwingWorker-pool-1-thread-33: [Fatal Error] motivation.xml:12:3: The element type "p" must be terminated by the matching end-tag "</p>".

It took me a while to figure out that the reason I couldn't see errors was that I had forgotten the <xi:include> of my new document.

Discussion

  • Eric Le Lay
    Eric Le Lay
    2012-09-11

    OK, I'll try to fix it this week :-)

     
  • Eric Le Lay
    Eric Le Lay
    2012-09-11

    • assigned_to: nobody --> kerik-sf
     
  • Eric Le Lay
    Eric Le Lay
    2012-09-16

    fixed in r22214.
    Prints a warning about buffer not parsed from root.
    Shows errors from 2nd parse if buffer not parsed from root.
    Thanks for reporting :-)

     
  • Eric Le Lay
    Eric Le Lay
    2012-09-16

    • status: open --> closed-fixed
     
  • Alan Ezust
    Alan Ezust
    2012-09-20

    Much better. but the warning that says "maybe you forgot the xi:include" - perhaps that should be a warning reported against the xml.root= file and sent to the errorlist instead of standard output?

     
  • Alan Ezust
    Alan Ezust
    2012-09-20

    • status: closed-fixed --> open-fixed
     
  • Alan Ezust
    Alan Ezust
    2012-09-20

    oops. ignore previous message. I see you got that working too. cool!

     
  • Alan Ezust
    Alan Ezust
    2012-09-20

    • status: open-fixed --> closed-fixed