In GATE developer, whenever I navigate back to the Messages window, I never know when anything happened therefore it makes it more difficult to determine when and how I ran into bother. It would be better if logging could accomodate
{code}
yy/mm/dd: WARN:Stack Dump:
gate.util.GateSaxException: Fatal XML parse error. Error details:
Message: Message
System ID: file:/media/PENDRIVE/xmlcalabash/output/3.19.xml
Public ID: not available
Line: 57
Column: 48
at gate.xml.SimpleErrorHandler.fatalError(SimpleErrorHandler.java:61)
at gate.xml.XmlDocumentHandler.fatalError(XmlDocumentHandler.java:548)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at gate.corpora.XmlDocumentFormat.unpackGeneralXmlMarkup(XmlDocumentFormat.java:308)
at gate.corpora.XmlDocumentFormat.unpackMarkup(XmlDocumentFormat.java:132)
at gate.corpora.XmlDocumentFormat.unpackMarkup(XmlDocumentFormat.java:83)
at gate.corpora.DocumentImpl.init(DocumentImpl.java:271)
at gate.Factory.createResource(Factory.java:384)
at gate.gui.NewResourceDialog$4.run(NewResourceDialog.java:225)
at java.lang.Thread.run(Thread.java:662)
{code}
Difficult to do this sensibly with things printed to System.out and System.err. Those places which already use a propper logger do do this correctly though.