More precisely: it throwed if it could not parse the xpath.
But it just gave null if there were some other exceptions...
So the easy thing would probably be to return null if there was an exception at evaluating XPath... (I think this is what most processors do anyways).
paul
Le 2 f�vr. 05, � 09:58, Brett Porter a �crit :
Hi Paul,
The issue I was having was a null pointer exception resulting from running the following:
<x:parse var="navXML" xml="" /> <x:set var="nav" value="$navXML/body" />
I think in the past, this used to set "nav" to null (presumably because navXML was an empty document, where now it is a null document?)
I'm now just skipping this code when xml is empty in the script.
Any thoughts on how this should be handled?
- Brett
Brett Porter wrote:
Hi Paul,
This fixed the original issue. I have another issue (as I mentioned before), if you run "maven -e xdoc" on maven-1/plugins/trunk/ashkelon you can see it. I'll investigate when I can, but hold off on that release in the mean time :)
- Brett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
