[Exist-development] XPathException deprecations....

[Andrzej J. T. <an...@ch...>]

...looks like many XPathException constructor signatures are now deprecated.  Bit of a pain to
create ErrorCode()s for custom errors, but so be it.

My question is whether the ErrorVal can be set safely to null for the constructor?

XPathException( Expression expr, ErrorCode errorCode, String errorDesc, Sequence errorVal,
		Throwable cause )

It looks like you can provide a description both in the ErrorCode object and separately in the
erroDesc. Can someone shed some light into why this is the case, and what happens if you provide
both or the description is missing in the ErrorCode or set to the empty string?  Seems a bit odd to
have both.

What is the errorVal used for?

Can you tell I'm trying to update some of our custom extensions/functions to 1.5/Trunk? LOL

Thanks!

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com