Subject:Bug using global variables in xquery module? Author:Jerry Beuree Date:26 May 2006 01:23 PM
I'm trying out the evaluation version of Stylus Studio 2006R2. I'm having problems getting it to work with some of our modules. They use global variables. For example:
When I try to import this module I get an error "Every global variable in a module must be in the module namespace [err:XQST0048]." It is in fact in the correct module namespace, so I'm suspecting this is a bug. Is there a way to workaround it?
Subject:Bug using global variables in xquery module? Author:Minollo I. Date:26 May 2006 01:36 PM
Yes, this is a bug in the internal XQuery processor in Release 2, BL591.
The problem has been fixed in the coming Release 3 version, available in mid June; in the meanwhile you may want to switch to DataDirect XQuery or Saxon as processors to test/develop your XQuery.
Subject:Bug using global variables in xquery module? Author:Jerry Beuree Date:26 May 2006 02:21 PM
Thanks for the quick response. DataDirect doesn't appear to support importing modules. Saxon works fine with the one exception that I can't seem to get Stylus Studio to let me set parameter values for the external variables in my xquery. It looks like it still uses the internal processor when displaying the Parameter Values tab of the scenario properties. Instead of showing my variables it gives me the "Every global variable in a module..." error again.