Re: problem with query builder

2017-11-18 Thread Claude Warren
Fix coming shortly but the work around is... change: Expr x = new NodeValueInteger(1) to: NodeValue nv = new NodeValueInteger(1) nv.asNode() Expr x = nv; Claude On Sat, Nov 18, 2017 at 3:48 PM, Claude Warren wrote: > Well done Andy. Right on the money, exactly what I

Re: fuseki 3.5.0 upload error

2017-11-18 Thread Andy Seaborne
JENA-1420 is resolved. Sorry for the problem. Andy On 18/11/17 02:38, Manuel Quintero Fonseca wrote: same error in fuseki 3.5.0 Result: failed with message "SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data" It works fine in fuseki 3.4.0 2017-11-07

Re: problem with query builder

2017-11-18 Thread Claude Warren
Well done Andy. Right on the money, exactly what I discovered. On Sat, Nov 18, 2017 at 3:39 PM, Andy Seaborne wrote: > c.f. NodeValue.getNode and NodeValue.asNode > > Presumably something calls getNode when it wanted asNode. > > > On 18/11/17 15:36, Claude Warren wrote: > >>

Re: problem with query builder

2017-11-18 Thread Andy Seaborne
c.f. NodeValue.getNode and NodeValue.asNode Presumably something calls getNode when it wanted asNode. On 18/11/17 15:36, Claude Warren wrote: This is a bug. The problem is that new NodeValueInteger(1); does not set the Node value that the rewriter is trying to rewrite and thus the null

Re: problem with query builder

2017-11-18 Thread Claude Warren
This is a bug. The problem is that new NodeValueInteger(1); does not set the Node value that the rewriter is trying to rewrite and thus the null pointer exception. I will get a fix out shortly. Claude On Fri, Nov 17, 2017 at 4:14 PM, Chris Dollin wrote: > Hi, >

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

2017-11-18 Thread Andy Seaborne
Sending https traffic to an http endpoint might explain the unexpected binary data like 0x03. Andy On 17/11/17 23:57, Marco Neumann wrote: so I did a quick test with a fresh build and it's recurring via https access requests on jetty. I think we can close this issue here in the AJF3.6.0