There's no need to hack cq, I think. Adding '&debug=1' to the location bar enables extra javascript logging and extra server logging. That should include the information you want.
-- Mike On 3 Dec 2011, at 10:52 , Jason Hunter wrote: > Trying that XPath in my own CQ in Chrome works. Might be some encoding > trouble with your system. > > Try putting the code in a .xqy file and see if it works. > > Try hacking CQ to see what it's seeing come in via the POST call. Is it > correct? > > Try changing the browser's stated encoding which often changes how it sends > the POST data. > > -jh- > > On Dec 3, 2011, at 10:35 AM, Michael Sokolov wrote: > >> I've run into some weirdness with element names like: >> >> <akl-erwähnungsort> >> >> //*[name()="akl-erwähnungsort"] >> >> works ok, but >> >> //akl-erwähnungsort >> >> fails when run from cq (in chrome) like this: >> >> [1.0-ml] XDMP-UNEXPECTED: (err:XPST0003) Unexpected token syntax error, >> unexpected Junk_, expecting $end >> >> I'm assuming this is a cq or browser issue, but can anyone shed any >> light here? >> >> -Mike >> _______________________________________________ >> General mailing list >> [email protected] >> http://developer.marklogic.com/mailman/listinfo/general > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
