- From: Philip Fennell <Philip.Fennell@marklogic.com>
- Date: Mon, 9 Jun 2014 16:21:58 +0000
- To: Philip Fennell <Philip.Fennell@marklogic.com>, "xproc-dev@w3.org" <xproc-dev@w3.org>
Received on Monday, 9 June 2014 16:22:21 UTC
Please ignore my previous e-mail. I've just answered my own question by wrapping the cxu:compare step in a try/catch but the error message is somewhat terse so I don't think I'll gain much from that. From: Philip Fennell <philip.fennell@marklogic.com<mailto:philip.fennell@marklogic.com>> Date: Monday, 9 June 2014 17:11 To: "xproc-dev@w3.org<mailto:xproc-dev@w3.org>" <xproc-dev@w3.org<mailto:xproc-dev@w3.org>> Subject: Is there an error report for cxu:compare? Resent-From: <xproc-dev@w3.org<mailto:xproc-dev@w3.org>> Resent-Date: Monday, 9 June 2014 17:12 Hello, I was just wondering if there is any way of getting any error report information out of the cxu:compare (XMLUnit) step when a comparison fails due to differences between the source and alternate input sources? Regards Philip
Received on Monday, 9 June 2014 16:22:21 UTC