|
|
 next
|
  Subject: XQuery debugger java exception
Author: Doug Hoople
Date: 04 Aug 2005 08:24 PM
|
Hi Ivan,
I've trimmed down my XML to a reasonable size, and in the process have had to toggle back and forth between the Saxon processer and the built-in, because the only error report I got back from Saxon was something generic like "static error in evaluating query" or something like that. This indicates that in debug, the Saxon parser barfs and doesn't say what's wrong. When run in preview, it does the same. To find out what's going on, it requires restoring the built-in for long enough to fix the problem.
Of course, when I switch, the first thing I encounter is the dreaded 'namespace saxon unrecognized' error that I was coming to you to avoid in the first place.
Sorry, but the debugger with Saxon isn't ready for prime time, at least not for full-time use.
Thanks anyway.
Doug
|
|
next
|
Subject: XQuery debugger java exception
Author: Doug Hoople
Date: 05 Aug 2005 12:13 PM
|
Look, not to put too fine a point on it, your marketing literature claims that you're the only IDE with debugging support for third-party XQuery processors. You're not. Not really. Not yet. Because the support provided is no better than not having the feature at all. If that's a difficulty that's simply inherited from the problem domain of integrating unlike products, then that's one thing, but you shouldn't be making claims to have solved a problem that hasn't been solved.
You can get any of your developers to write just about anything in XQuery from scratch, and in the process of bumping into things as simple as syntax errors, you'll have so little information about what's going on, you'll scream. I doesn't take much of a flaw to get the whole thing to go belly up. A simple QA cycle with just about any script still under active development should have turned this up, so please don't ask me for diagnostics.
The build was whatever was on the Professional evaluation download queue yesterday, Thursday, August 4, 2005.
Maybe it's just that particular build that introduced a single, simple regression that caused the whole 'third party integration' feature to fail. I suspect, though, that it's really a case of an advertised feature not being ready.
I hope I'm wrong, because the world's ready for this to work. I certainly am.
Good luck to you in your efforts.
|
|
next
|
Subject: XQuery debugger java exception
Author: Doug Hoople
Date: 05 Aug 2005 09:00 PM
|
It's a pretty big defect then, so you have to forgive me. If developers all over the world are using this debugger with this XQuery processor, then I've stumbled into some weird corner case. It's hard to imagine, though.
I'm been unable to set a breakpoint or step into the simplest of queries. Like the following:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<
declare namespace dd = "urn:thisisatest";
declare function dd:testing123( $input as xs:string ) as xs:string
{
"testing123"
};
<x>{dd:testing123("something really simple")}</x>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<
I'm an XQuery newbie, so I may have done something really stupid, but this seems pretty straightforward to me. I still get a NullPointerException when I try to set a breakpoint. Like I said, maybe you've just had a whopper of a regression in this build (377, by the way).
The Output window shows the following exception information:
com.stylusstudio.debugger.utils.UserStopException: XQuery Processing has been stopped
at com.stylusstudio.debugger.saxon.DebugRemote.sendNotification(DebugRemote.java:221)
at com.stylusstudio.debugger.saxon.DebugRemote.sendError(DebugRemote.java:176)
at com.stylusstudio.debugger.saxon.DebugTracer.sendError(DebugTracer.java:96)
at com.stylusstudio.debugger.saxon.CSaxonXQueryDriver.run(CSaxonXQueryDriver.java:170)
at java.lang.Thread.run(Unknown Source)
When I run the Saxon parser from the command line, it executes fine, but seems to complain a bit about the namespace declaration (I fiddled with a couple of format variants and got the same results). I get the following:
D:\XQuery>java net.sf.saxon.Query -T -TJ testing234.xquery
Loading urn:thisisatest
No Java class urn:thisisatest could be loaded
<trace saxon-version="8.4" >
<element name="x" line="7" column="1" module="testing234.xquery">
<function name="dd:testing123" line="2" column="1" module="testing234.xquery">
</function>
</element>
</trace>
<?xml version="1.0" encoding="UTF-8"?>
<x>testing123</x>
D:\XQuery>
I have to admit that having the trace feedback from the command line gives me more information to work with, and makes the situation a bit more bearable. I was at least able to ascertain what my errors were in cleaning up my syntax problems.
Still, from within Stylus Studio, I can't step, I can't break, I can't watch. I hope you're right, and that it's simply a defect. Ideally, I'll have done something really obvious and stupid, for which there's a simple workaround. It would also not be so bad if it were something for which the fix is relatively trivial. I just don't understand how I'm the only developer in the world who's had the misfortune to step into this one, seeing how basic it is. Just my luck.
Thanks.
Doug Hoople
|
|
|
|
|
top