I believe this has been fixed now, so download and try with the latest rest server, http://wiki.neo4j.org/content/Getting_Started_REST
2010/4/13 Alastair James <[email protected]> > Cheers. Sorry, I probably should have filed this in the Trac. > > Al > > On 13 April 2010 00:15, Tobias Ivarsson > <[email protected]>wrote: > > > On Tue, Apr 13, 2010 at 1:01 AM, Alastair James <[email protected]> > > wrote: > > > > > Hi! > > > > > > > > > > The example you mentioned: "\u2018Hello world\u2018", is probably > > > properly > > > > escaped since 2018 is LEFT SINGLE QUOTATION MARK [2], and quotation > > marks > > > > should be escaped, but is this the sequence you are experiencing > > problems > > > > with? If that gets returned unescaped, that could be a problem, but > if > > > it's > > > > another char, like \u00f6, then it should be allowed to be > represented > > > > unescaped as a proper unicode char. > > > > > > > > > > Yes, that is an example string that is failing. However, \u2018 is a > > fancy > > > quote (http://www.fileformat.info/info/unicode/char/2018/index.htm) > not > > > one > > > of the quotes that needs to be encoded, so it should not matter if its > > > returned unencoded or not (its part of the JSON encoding). > > > > > > > > > > It might still be a bug though, so if you could provide some more > > details > > > > that would be great. Also could you check if the truncation of > messages > > > > occurs in your client due to decoding issues, on the server or on the > > > wire. > > > > > > > > > > The web service returns a HTTP CONTENT LENGTH header of the same length > > and > > > is received by my client, so I think its a bug. > > > > > > I tell you what I think the issue is, I noticed the enclosed example > > > contains two unicode charcters, each of which is a three byte sequence > in > > > UTF-8. > > > > > > The response is exactly 4 characters too short (mising ut"}), so its > > almost > > > like the output length is the number of characters not the number of > > bytes. > > > > > > Looking at GenericWebService.java -> line 86 -> method addHeaders > > > > > > builder = builder.header( HttpHeaders.CONTENT_LENGTH, > > > String.valueOf( > > > builder.clone().build().getEntity().toString().length() ) ); > > > > > > Won't that set the content length to the number of characters NOT > bytes? > > > > > > > Yes, I believe you've nailed it, that does very much look like the cause > of > > this. I'll get on to fixing it in the morning. > > > > -- > > Tobias Ivarsson <[email protected]> > > Hacker, Neo Technology > > www.neotechnology.com > > Cellphone: +46 706 534857 > > _______________________________________________ > > Neo mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > > > > -- > Dr Alastair James > CTO James Publishing Ltd. > http://www.linkedin.com/pub/3/914/163 > > www.worldreviewer.com > > WINNER Travolution Awards Best Travel Information Website 2009 > WINNER IRHAS Awards, Los Angeles, Best Travel Website 2008 > WINNER Travolution Awards Best New Online Travel Company 2008 > WINNER Travel Weekly Magellan Award 2008 > WINNER Yahoo! Finds of the Year 2007 > > "Noli nothis permittere te terere!" > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [[email protected]] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
