For the example you've posted, there's no compilation error with <assert> XPath expression and the <assert> has returned true for the XML instance document you've posted.
The <assert> you've cited seems to have a lengthy XPath expression. Unless there's a strong reason to write such lengthy <assert> XPath expressions, these should be refactored (for example, by breaking these into multiple asserts) to have a reasonable logical complexity. On Thu, May 9, 2013 at 7:42 PM, Jim Barnett <jim.barn...@genesyslab.com> wrote: > Are there tools that will help me debug a complex assertion? I’ve tried > using trace, but it doesn’t seem to print out messages when it’s inside an > ‘every’ or a ‘some’. I’ve attached the example I’m trying to debug. The > assertion in line 26 of the schema should reject the <transition> in line 7 > of sample.scxml, but it doesn’t (so validation succeeds). I can’t tell if > there’s a logical error in my schema, or if I’m not using some element > correctly. Can someone give me some hints on how to debug the assertion’s > application? > > > > Thanks in advance, > > Jim Barnett -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
