From: Dannes W. <da...@ex...> - 2012-01-26 21:54:54
|
Hi Loren, the variable must be bound, if it isn't I forgot to do it, and need to repair :-) the interesting question is……. what on earth should we put in it? I added two additional variables, $exerr:java-stack-trace and $exerr:function-stack-trace , providing exist-db specific information. Will be used by eXide in near future. if you have some a (one) good idea to put in, please let me know……. cheers Dannes -- Dannes Wessels eXist-db Open Source Native XML Database e: da...@ex... w: http://www.exist-db.org On Thursday, January 26, 2012 at 22:05 , Loren Cahlander wrote: > Dannes, > > Are there any plans to implement $err:additional? > > err:additional item()* > > Implementation-defined. This variable must be bound so that a query can reference it without raising an error. The purpose of this variable is to allow implementations to provide any additional information that might be useful. > > > On Jan 15, 2012, at 12:34 PM, di...@us... (mailto:di...@us...) wrote: > > > Revision: 15683 > > http://exist.svn.sourceforge.net/exist/?rev=15683&view=rev > > Author: dizzzz > > Date: 2012-01-15 18:34:32 +0000 (Sun, 15 Jan 2012) > > Log Message: > > ----------- > > [update] Updated try-catch expression to match the new XQuery3 specification. > > > > Example: > > xquery version '3.0'; > > try { > > fn:error(fn:QName('http://www.w3.org/2005/xqt-errors', 'err:FOER0000')) > > } catch * { > > $err:code, $err:value, " module: ", > > $err:module, "(", $err:line-number, ",", $err:column-number, ")" > > } > > > > the WiKi shall be updated accordingly |