On further investigation, this problem only seems to affect one particular character, E000. I've tried this with E001, E002, etc and the server seems completely OK with those.
I'm cc'ing ML support, in case they can shed any light on this. -Steve On 08/11/2010 14:23, Steve Mallen wrote: > Hi all, > > I've just upgraded my 3.2 database to 4.1, and I'm now getting errors thrown > with existing XQuery code. > > Our XML data contains private use characters which are used for certain > features. The use of these now seems to be throwing XDMP-HEXREF exceptions. > > As a test, the following works in cq: > > let $string := "♭" > return $string > > But the following does not work: > > let $string := "" > return $string > > I get an Internal Server Error, with the following nested exception: > > XDMP-HEXREF: (err:XPST0003) Invalid hex character reference > > This used to work in 3.2, and the range [#xE000-#xFFFD] is valid according the > XML spec. > > Has anyone seen this, or knows if it is a bug? > > Many thanks, > -Steve > -- Senior Software Engineer, Semantico Limited <mailto:[email protected]> <tel:+44.1273.358239> Registered in England and Wales no. 03841410, VAT no. GB-744614334. Registered office Lees House, 21-23 Dyke Road, Brighton BN1 3FE, UK. Check out all our latest news and thinking on the Discovery blog http://blogs.semantico.com/discovery-blog/ _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
