Hi Mike,
That's a bug, which I fixed in version 4.2-1. It has not as yet been
back-ported to 4.1.
John
On 03/12/11 19:28, Michael Sokolov wrote:
> Actually this doesn't seem to have anything to do with cq. A file with
>
> //akl-erwähnungsort
>
> in it produces an error too when run via an HTTP service.
>
> xdmp:eval("//akl-erwähnungsort")
>
> fails too, so it doesn't seem to have anything to do with reading in the
> file either.
>
> The server is linux 4.1.6, has LANG=en_US.UTF-8
>
> -Mike
>
> On 12/3/2011 2:00 PM, Michael Blakeley wrote:
>> 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
--
John Snelson, Senior Engineer http://twitter.com/jpcs
MarkLogic Corporation http://www.marklogic.com
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general