View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000027CLAMModule: Corepublic2012-06-08 08:402012-06-08 08:40
Assigned To 
PlatformOSOS Version
Product Version1.4 (current stable release) 
Target VersionFixed in Version 
Summary0000027: libxml++ errors are always shown on the console but no way to get them progamatically
DescriptionWhen using the libxml++ backend for xml and an error occurs (syntax, system...) the libxml library outputs the error to the standard error but what we want is to get the error string and make it available to the program so it can be shown, for example on the user interface or printed into a log.

Steps To ReproduceThe libxml unit tests run some failing examples that get printed into the standard out (nagging us a lot with the test output!) so it would be the nicest way to reproduce it in order to fix it. If you run them, you will read:

:1: parser error : Document is empty
ument />
...:1: parser error : Attribute attribute redefined
<TestDoc><Element attribute="Attribute value" attribute="other value">Content<In
.:1: parser error : Opening and ending tag mismatch: Unclosed line 1 and Element
><Element attribute="Attribute value">Content<Unclosed><InnerElement/></Element>
.:1: parser error : Opening and ending tag mismatch: Element line 1 and Unopened
<TestDoc><Element attribute="Attribute value">Content<InnerElement/></Unopened><
......:1: parser error : Opening and ending tag mismatch: UnclossedChild line 1 and LoadedRoot
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2012-06-08 08:40 dgarcia New Issue

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker