Project

Profile

Help

Forums » Help »

unexpected SENR0001 error

Added by Anonymous over 18 years ago

Legacy ID: #3795937 Legacy Poster: marcvc (marcvc)

Michael, consider the following query <e>{ <e/>, attribute a {'a'} }</e> With Saxon 8.7.x it results in the following error: SENR0001: Cannot serialize a free-standing attribute node (a) Rather than a serialization error, I would have expected XQTY0024. Thanks, Marc


Replies (2)

RE: unexpected SENR0001 error - Added by Anonymous over 18 years ago

Legacy ID: #3796033 Legacy Poster: Michael Kay (mhkay)

Yes. Unfortunately it sometimes happens that the same code is used internally for a number of different user-level operations, and in these cases it can be quite difficult to disentangle the error codes. I'll have another look at it.

RE: unexpected SENR0001 error - Added by Anonymous over 18 years ago

Legacy ID: #3801710 Legacy Poster: Michael Kay (mhkay)

I have now fixed this case - hopefully without breaking any other cases. As mentioned, it's quite tricky with this error to distinguish the different situations that are detected by common code but need to produce different error codes. In fact I've gone further and many cases of this error, including this example, will now be detected statically.

    (1-2/2)

    Please register to reply