W3C home > Mailing lists > Public > xproc-dev@w3.org > December 2010

Re: XProc error messages driving me crazy!

From: Tony Rogers <tony@gonk.net>
Date: Wed, 15 Dec 2010 10:12:57 -0500
Message-Id: <7B4CA847-B367-42E9-85EE-2AEFB1814952@gonk.net>
Cc: XProc Dev <xproc-dev@w3.org>
To: George Cristian Bina <george@oxygenxml.com>
Hello George,

The error as printed in this email is verbatim from Oxygen. I simply right-clicked the error from the errors tab an selected “Copy”. As you can see, there is no line number. :(

I'm used to Oxygen being unbelievably helpful with its error messages, which is why this case drove me crazy. Similar messages have been happening to me during this XProc project, which is unfortunate. 

More unfortunate, however, is that this project is for school, and I'm already a bit behind (!), so I simply tried one thing after another until I got it working again.  I don't have a backup of the files as they used to be to reproduce the error. Sorry!  :(. 

(ASIDE: 
     I do try vey hard to be good about reporting errors in Oxygen—and I have been encourages to continue doing so because the support always responds very quickly and specifically to me. No automated “Bug report received. Thanks. We'll get back to you soon. Maybe. ”

Makes me feel very appreciated and want to keep reporting things as I find them. Feel free to pass that on to you co-workers. :-)

I ended up commenting out my steps one by one until I had it down to 1 main step & 1 library step. Finally I commented out pieces of the library step until I realized that the complaint was about some XPaths in a couple of p:deletes and p:inserts. I fiddled with it and after about 4 or 5 very fast attempts (this is the final project of the semester for me!) I got it working. 

I know it's not much and a sample pipeline is preferable, but that's all I can give you this time. I hope it is of some small help!

—Tony

Sent from my iPod Touch

On Dec 15, 2010, at 8:21 AM, George Cristian Bina <george@oxygenxml.com> wrote:

> Hi Tony,
> 
> oXygen should report any location information if Calabash provides it. If you send us a sample that we can use to reproduce the issue then we can investigate to see if there is anything we can do better.
> 
> Best Regards,
> George
> -- 
> George Cristian Bina
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
> 
> On 12/14/10 6:02 PM, Tony Rogers wrote:
>> Using Oxygen 12 with bundled Calabash (0.9.23 I believe?) on Mac OS X
>> 10.6 (Snow Leopard).
>> 
>> I just got the following error message:
>> 
>>    SystemID:
>>    /Users/amrogers/Developer/Projects/oXygen_workspace/edu.umd/terpconnect/model/documents/201008/INFM298I/Final
>>    Project/xproc.xpl
>>    Engine name: Calabash XProc
>>    Severity: error
>>    Description: XD0045 : XProc error err:XD0045 Invalid QName {}
>> 
>> 
>> I have been trying to pinpoint what is causing this since late yesterday
>> afternoon, and I am nearly pulling my hair out of frustration because I
>> have no idea what this message is referring to.
>> 
>> WHICH name is invalid?
>> In WHICH STEP did it occur?
>> WHAT LINE is mucking up my pipeline?
>> 
>> Aaaaarrrrggghhhh!
>> 
>> …
>> …
>> …
>> 
>> Sorry, I just needed to get that out. Seriously, I love Calabash. It’s
>> opened amazing new doors for me. I’m just frustrated as hell at the
>> moment and I needed to vent. :)
>> 
>> 
>> 
>> —Tony
> 
Received on Wednesday, 15 December 2010 15:14:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 15 December 2010 15:14:35 GMT