Project

Profile

Help

Forums » Help »

Is XT0380 still applicable?

Added by Anonymous over 19 years ago

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

Michael, is error XT0380 still applicable to Saxon 8.3 I would expect the following to work? <e>{fn:QName((),"a")}</e> Thanks, Marc


Replies (2)

RE: Is XT0380 still applicable? - Added by Anonymous over 19 years ago

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

No, this is a relic. Your example is working in my current build, more or less by accident. The test for this condition at lines 398-402 of net.sf.saxon.event.ComplexContentOutputter: if (item instanceof QNameValue) { DynamicError err = new DynamicError("Cannot add a QName value to the content of an element"); err.setErrorCode("XT0380"); throw err; } can safely be removed.

RE: Is XT0380 still applicable? - Added by Anonymous over 19 years ago

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

No, this error condition was removed from the latest XSLT and XQuery drafts, and the test should have been removed from the code. The test if (item instanceof QNameValue) { DynamicError err = new DynamicError("Cannot add a QName value to the content of an element"); err.setErrorCode("XT0380"); throw err; } at line 398 in net.sf.saxon.event.ComplexContentOutputter can safely be deleted.

    (1-2/2)

    Please register to reply