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

David Buchmann commented on JCR-3985:
-------------------------------------

hi alfu,

using https://github.com/jackalope/JavaDavexClient, i have this code in 
src/Client.java:

{code}
        String url = "http://localhost:8080/server/";;
        String workspace = "testsWorkspace";

        DavexClient Client = new DavexClient(url);
        Repository repo = Client.getRepository();
        Credentials sc = new SimpleCredentials("admin","admin".toCharArray());
        Session s = repo.login(sc,workspace);
        ValueFactory f = s.getValueFactory();

        QueryManager qm = s.getWorkspace().getQueryManager();
        Query q = qm.createQuery("SELECT * FROM [nt:unstructured] AS a WHERE 
ISCHILDNODE(a, [/tests_query_encoding/test-2e])", Query.JCR_SQL2);
        QueryResult r = q.execute();

        RowIterator i = r.getRows();
        while (i.hasNext()) {
            Row row = i.nextRow();
            System.out.println(row.getNode().getPath());
        }
{code}

It fails on the line q.execute();

thanks for looking at this!

> 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
(v6.3.4#6332)

Reply via email to