Important error details suppressed by p:error

• From: David Cramer <david@thingbag.net>
• Date: Thu, 19 Dec 2013 15:35:45 -0600
• To: XProc Dev <xproc-dev@w3.org>
• Message-ID: <52B366B1.7070203@thingbag.net>

Hi there,
I have a validation step in a pipeline with the following in the p:catch:

             <p:error code="psch:Invalid">
                 <p:input port="source">
                     <p:pipe port="error" step="catch"/>
                 </p:input>
             </p:error>

When errors occur, they're reported like so:

Dec 19, 2013 3:26:26 PM com.xmlcalabash.util.DefaultXProcMessageListener
error
SEVERE:
product_schema_def/xpl/productSchema.xpl:0:psch:Invalid:net.sf.saxon.trans.XPathException:
Cannot compare MinOccurs to xs:string
Dec 19, 2013 3:26:26 PM com.xmlcalabash.drivers.Main error
SEVERE: Unknown error

If I set up a secondary report port and passing it through an xslt, I
can get it to spit out the full error:

<c:errors xmlns:c="http://www.w3.org/ns/xproc-step">
   <error xmlns="http://www.w3.org/ns/xproc-step"
          xmlns:err="http://www.w3.org/2005/xqt-errors"
          code="err:XPTY0004"
          type="fatal-error"

href="file:/home/dcramer/Documents/rax/standard-usage-schemas-myfork/product_schema_def/xsl/productSchema-standalone.xsl"
          line="300">net.sf.saxon.trans.XPathException: Cannot compare
MinOccurs to xs:string</error>
</c:errors>

I'm puzzled though as to why p:error suppresses critical information
like the file and line in which the error occurred to begin with. Is
there some easy way to tell p:error to provide all the details?

Regards,
David

Received on Thursday, 19 December 2013 21:36:19 UTC