jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alfusainey Jallow (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3985) jackrabbit remoting fails on number followed by "e"
Date Tue, 16 Aug 2016 09:43:20 GMT

    [ https://issues.apache.org/jira/browse/JCR-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422500#comment-15422500

Alfusainey Jallow commented on JCR-3985:

hi david,

i am not too familiar with jcr query so may [~anchela], [~chetanm] or [~mduerig] can have
a look.

yes but imho, ISCHILDNODE accepts a string but the string should contain a valid decimal string
representation (if any). 'node-1e' is not a valid decimal since it is not of the correct form.

maybe someone will comment soon on the issue so that it gets resolved

> jackrabbit remoting fails on number followed by "e"
> ---------------------------------------------------
>                 Key: JCR-3985
>                 URL: https://issues.apache.org/jira/browse/JCR-3985
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-spi
>    Affects Versions: 2.12.1
>            Reporter: David Buchmann
> with our PHP client using the jackrabbit remoting, we found a very strange bug. when
we try to query for a node with ISCHILDNODE and a name that has -, . or %, followed by a number
and then followed by e or E, we get an error 400 response. I tried the same with a simple
java client to see if we do something wrong on our side, but the result is the same.
> so what does not work are names like `-2e`, `.3e` or `%0E`
> the problem does not happen if the character before <NUMBER>e is something else,
and it does not happen with other letters than "e". it happens with all numbers however. 

This message was sent by Atlassian JIRA

View raw message