[jira] [Commented] (JENA-1239) fuseki should not autocreate a config.ttl file if a configuration file is specified on the command line

[Dan Pritts (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405310#comment-16405310
 ] 

Dan Pritts commented on JENA-1239:
--

Just installed 3.6.0 and this behavior is still present.

> fuseki should not autocreate a config.ttl file if a configuration file is 
> specified on the command line
> ---
>
> Key: JENA-1239
> URL: https://issues.apache.org/jira/browse/JENA-1239
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Fuseki 2.4.0
> Environment: RHEL6, openjdk 1.8.0_101
>Reporter: Dan Pritts
>Priority: Minor
>
> I use the command line to specify a configuration file when I start fuseki.  
> My config is not in $FUSEKI_BASE/config.ttl
> Even so, fuseki autocreates a config.ttl in $FUSEKI_BASE if one does not 
> already exist.  
> This could easily be confusing to the next person who comes along (heck, it 
> confused me when rolled back around to fuseki today after being away from it 
> for a few weeks).  So, I propose that you add a check (do I have a config 
> file?) before you create the default config.ttl.  
> thanks



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (JENA-1509) RDFConnectionRemote does not execute update( UpdateRequest )

[Claude Warren (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claude Warren resolved JENA-1509.
-
   Resolution: Fixed
Fix Version/s: Jena 3.7.0

> RDFConnectionRemote does not execute update( UpdateRequest )
> 
>
> Key: JENA-1509
> URL: https://issues.apache.org/jira/browse/JENA-1509
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.7.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Major
> Fix For: Jena 3.7.0
>
>
> If an UpdateRequest is constructed and passed to the 
> RDFConnectionRemote.update() method the string value is lost and the results 
> is an "update string may not be null" exception.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: git.apache.org issue?

[ajs6f]

I had no trouble doing that checkout a few moments ago, but I am on $job 
networking with very good throughput and I work only a few miles from Ashburn, 
Virginia (more data centers than you can shake a stick at). I was getting 
between 10 and 12 MiB/s. The total transfer was 352.82 MiB, so maybe you could 
try downloading a large file of about that size from somewhere else in Apache 
infrastructure to see if it's your connection to Apache.

Otherwise, you can always checkout the Github mirror, which is the same code: 
g...@github.com:apache/jena.git

 
ajs6f

> On Mar 19, 2018, at 7:10 AM, Claude Warren  wrote:
> 
> I have tried to execute
> 
> git clone git://git.apache.org/jena.git
> 
> four times and each time I get:
> 
> Cloning into 'jena'...
> remote: Counting objects: 349618, done.
> remote: Compressing objects: 100% (64022/64022), done.
> fatal: The remote end hung up unexpectedly23.70 MiB | 275.00 KiB/s
> fatal: early EOF
> fatal: index-pack failed
> 
> and no jena directory created.
> 
> I have plenty of space so I am wondering if there is an issue on the apache
> server.  Though perhaps  the issue is with my ISP.
> 
> Claude
> 
> 
> 
> -- 
> I like: Like Like - The likeliest place on the web
> 
> LinkedIn: http://www.linkedin.com/in/claudewarren

Re: number of git clones?

[ajs6f]

This is a great bunch of advice from Rob. The only thing I want to add to it is 
that I was recently hepped to a really useful tool that Github has created:

https://github.com/github/hub

It's a drop-in replacement for `git`, so all of Rob's notes below (and anything 
else you find to work with git) will keep working, no change. But it offers 
some additional commands for working with Github-based projects.

For example, if I wanted to take a look at Chris' recent PR for JENA-1506, I 
can just type:

git checkout https://github.com/apache/jena/pull/385

(because I have `hub` aliased to `git`) and hub handles the bookkeeping 
(fetching, pulling, assigning branch names, etc.) to give me:

➜  jena git:(master) git checkout https://github.com/apache/jena/pull/385
remote: Counting objects: 67, done.
remote: Compressing objects: 100% (35/35), done.
remote: Total 67 (delta 18), reused 56 (delta 8), pack-reused 1
Unpacking objects: 100% (67/67), done.
From git://github.com/BuddhistDigitalResourceCenter/jena
 * [new branch]JENA-1506-PR -> 
BuddhistDigitalResourceCenter/JENA-1506-PR
Branch BuddhistDigitalResourceCenter-JENA-1506-PR set up to track remote branch 
JENA-1506-PR from BuddhistDigitalResourceCenter.
Switched to a new branch 'BuddhistDigitalResourceCenter-JENA-1506-PR'
➜  jena git:(BuddhistDigitalResourceCenter-JENA-1506-PR)

and with one command and knowing nothing about where Chris' branch is coming 
from, I'm ready to go, to examine or merge the PR. (Of course, I'm not going to 
merge anything, just an example!)

hub provides some other useful tools, for forking on Github and sending PRs and 
so forth. Well-worth the price of admission!

ajs6f

> On Mar 19, 2018, at 6:44 AM, Rob Vesse  wrote:
> 
> You can have multiple remote repositories defined in your local working copy. 
>  Here's the list of my defined remotes on my Jena working copy:
> 
>> git remote -vv
> afs   https://github.com/afs/jena.git (fetch)
> afs   https://github.com/afs/jena.git (push)
> originhttps://git-wip-us.apache.org/repos/asf/jena.git (fetch)
> originhttps://git-wip-us.apache.org/repos/asf/jena.git (push)
> rvessessh://g...@github.com/rvesse/jena.git (fetch)
> rvessessh://g...@github.com/rvesse/jena.git (push)
> 
> You can use git remote add   to add additional remotes and various 
> other git remote commands to manipulate these
> 
> When doing certain remote operations - pull/push/fetch - then you just need 
> to be more explicit about where to push/pull from.  For example to push a new 
> dev branch to my github clone:
> 
>> git push -u rvesse 
> 
> Where  is the local branch name you are wanting to push
> 
> Or to pull a specific branch:
> 
>> git pull  
> 
> This tries to pull updates for the given branch based on its locally set 
> upstream branch, git branch -vv shows details of your local branches and 
> their corresponding remotes:
> 
>> git branch -vv
>  JENA-1405   5937830 [rvesse/JENA-1405] Use better logging approach 
> (JENA-1405)
>  JENA-1407   9e2b4ce [rvesse/JENA-1407: ahead 1] Change degree of test 
> parallelism (JENA-1407)
>  JENA-1434   8df3702 [rvesse/JENA-1434] Minor fixes to new code 
> (JENA-1434)
>  JENA-1486   0eeb40d [rvesse/JENA-1486] Make sure to use datasets 
> transactionally (JENA-1486)
>  JENA-1497   44683c4 [rvesse/JENA-1497] Rename test cases and fix 
> warnings (JENA-1497)
>  JENA-50777a69f1 [origin/JENA-507: gone] Merge branch 'master' into 
> JENA-507
>  JENA-541cbc2dc2 Initial work on custom headers for SPARQL Updates 
> (JENA-541)
>  JENA-8933ab3138 More experimentation with splitting BZip2 inputs
>  jena-db-testing 10441d7 [afs/jena-db-testing] Check .delete() in beforeTest
>  jena2   9bc5aa9 [origin/jena2] Yet more fixes and test cases for 
> assignment inlining (JENA-780)
> * master  2e732b4 [origin/master: behind 2] Merge branch 'JENA-1497'
>  obfuscate   08bdbc3 [rvesse/obfuscate] Add naive obfuscation provider
> 
> Or:
> 
>> git fetch --all
>> git pull /
> 
> And merging a specific remote branch:
> 
>> git fetch --all
>> git merge /
> 
> Similarly to checkout a specific remote branch locally:
> 
>> git fetch --all
>> git checkout -B  --track /
> 
> You just need to be a little careful about doing pull/push without being 
> explicit about the target remote as otherwise you'll go to/from the default 
> (usually origin) which may not always be desired
> 
> Rob
> 
> On 19/03/2018, 10:31, "Claude Warren"  wrote:
> 
>What process are you using to keep your working copy of Jena (assuming you
>have a clone on github) from the true master copy of Jena such that you can
>create pull requests from you copy and merge them into the master.
> 
>So far the only way I have found to do this is to keep 2 copies of the code
>in 2 different local git repositories.  the first I pull from master,
>update, test, etc. check into my 

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404685#comment-16404685
 ] 

ASF GitHub Bot commented on JENA-632:
-

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r175409690
  
--- Diff: 
jena-arq/src/main/java/org/apache/jena/query/ResultSetFormatter.java ---
@@ -516,6 +520,41 @@ static public void outputAsJSON(boolean booleanResult)
 static public void outputAsJSON(OutputStream outStream, boolean 
booleanResult)
 { output(outStream, booleanResult, SPARQLResultSetJSON) ; }
 
+/** Output an iterator of JSON values.
+*
+* @param outStream output stream
+* @param jsonItems The JSON values
+*/
+   public static void outputAsJSON(OutputStream outStream, 
Iterator jsonItems)
+   {
+   JSWriter jWriter = new JSWriter(outStream) ;
+   jWriter.startArray() ;
+   jWriter.startOutput() ;
+   while (jsonItems.hasNext()) 
+   {
+   jWriter.startObject() ;
+   JsonObject jsonItem = jsonItems.next() ;
+   for (Entry entry: jsonItem.entrySet()) 
+   {
+   JsonValue value = entry.getValue() ;
+   String val = "";
+   if (value.isString()) {
--- End diff --

"outputAsJSON" is a bit confusing because the other functions of the same 
name produce SPARQL results in JSON.  How about "output"?

In the code, numbers still come out as strings.

JSWriter seems to be only good for its current usage. The code below seems 
to work: it manages the outer array itself and uses `JsonValue.output` to write 
each item.

```
 public static void outputAsJSON(OutputStream outStream, 
Iterator jsonItems)
{
IndentedWriter out = new IndentedWriter(outStream);
out.println("[");
out.incIndent();

while (jsonItems.hasNext()) {
JsonObject jsonItem = jsonItems.next() ;
jsonItem.output(out);
if ( jsonItems.hasNext() )
out.println(" ,");
else
out.println();
}
out.decIndent();
out.println("]");
out.flush();
}
```   


> Generate JSON from SPARQL directly.
> ---
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, Fuseki
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>Priority: Minor
>  Labels: java, javacc
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL) 
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user 
> community, basic understanding of HTTP and content negotiation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] jena pull request #114: JENA-632: Generate JSON from SPARQL directly

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r175409690
  
--- Diff: 
jena-arq/src/main/java/org/apache/jena/query/ResultSetFormatter.java ---
@@ -516,6 +520,41 @@ static public void outputAsJSON(boolean booleanResult)
 static public void outputAsJSON(OutputStream outStream, boolean 
booleanResult)
 { output(outStream, booleanResult, SPARQLResultSetJSON) ; }
 
+/** Output an iterator of JSON values.
+*
+* @param outStream output stream
+* @param jsonItems The JSON values
+*/
+   public static void outputAsJSON(OutputStream outStream, 
Iterator jsonItems)
+   {
+   JSWriter jWriter = new JSWriter(outStream) ;
+   jWriter.startArray() ;
+   jWriter.startOutput() ;
+   while (jsonItems.hasNext()) 
+   {
+   jWriter.startObject() ;
+   JsonObject jsonItem = jsonItems.next() ;
+   for (Entry entry: jsonItem.entrySet()) 
+   {
+   JsonValue value = entry.getValue() ;
+   String val = "";
+   if (value.isString()) {
--- End diff --

"outputAsJSON" is a bit confusing because the other functions of the same 
name produce SPARQL results in JSON.  How about "output"?

In the code, numbers still come out as strings.

JSWriter seems to be only good for its current usage. The code below seems 
to work: it manages the outer array itself and uses `JsonValue.output` to write 
each item.

```
 public static void outputAsJSON(OutputStream outStream, 
Iterator jsonItems)
{
IndentedWriter out = new IndentedWriter(outStream);
out.println("[");
out.incIndent();

while (jsonItems.hasNext()) {
JsonObject jsonItem = jsonItems.next() ;
jsonItem.output(out);
if ( jsonItems.hasNext() )
out.println(" ,");
else
out.println();
}
out.decIndent();
out.println("]");
out.flush();
}
```   


---

[jira] [Commented] (JENA-1509) RDFConnectionRemote does not execute update( UpdateRequest )

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404649#comment-16404649
 ] 

ASF GitHub Bot commented on JENA-1509:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/387


> RDFConnectionRemote does not execute update( UpdateRequest )
> 
>
> Key: JENA-1509
> URL: https://issues.apache.org/jira/browse/JENA-1509
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.7.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Major
>
> If an UpdateRequest is constructed and passed to the 
> RDFConnectionRemote.update() method the string value is lost and the results 
> is an "update string may not be null" exception.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (JENA-1509) RDFConnectionRemote does not execute update( UpdateRequest )

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404648#comment-16404648
 ] 

ASF subversion and git services commented on JENA-1509:
---

Commit 3604ddff2d7465205f3935391862df1bac681a30 in jena's branch 
refs/heads/master from [~cla...@xenei.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=3604ddf ]

fix for JENA-1509

> RDFConnectionRemote does not execute update( UpdateRequest )
> 
>
> Key: JENA-1509
> URL: https://issues.apache.org/jira/browse/JENA-1509
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.7.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Major
>
> If an UpdateRequest is constructed and passed to the 
> RDFConnectionRemote.update() method the string value is lost and the results 
> is an "update string may not be null" exception.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] jena pull request #387: fix for JENA-1509

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/387


---

git.apache.org issue?

[Claude Warren]

I have tried to execute

git clone git://git.apache.org/jena.git

four times and each time I get:

Cloning into 'jena'...
remote: Counting objects: 349618, done.
remote: Compressing objects: 100% (64022/64022), done.
fatal: The remote end hung up unexpectedly23.70 MiB | 275.00 KiB/s
fatal: early EOF
fatal: index-pack failed

and no jena directory created.

I have plenty of space so I am wondering if there is an issue on the apache
server.  Though perhaps  the issue is with my ISP.

Claude



-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

Re: number of git clones?

[Rob Vesse]

You can have multiple remote repositories defined in your local working copy.  
Here's the list of my defined remotes on my Jena working copy:

> git remote -vv
afs https://github.com/afs/jena.git (fetch)
afs https://github.com/afs/jena.git (push)
origin  https://git-wip-us.apache.org/repos/asf/jena.git (fetch)
origin  https://git-wip-us.apache.org/repos/asf/jena.git (push)
rvesse  ssh://g...@github.com/rvesse/jena.git (fetch)
rvesse  ssh://g...@github.com/rvesse/jena.git (push)

You can use git remote add   to add additional remotes and various 
other git remote commands to manipulate these

When doing certain remote operations - pull/push/fetch - then you just need to 
be more explicit about where to push/pull from.  For example to push a new dev 
branch to my github clone:

> git push -u rvesse 

Where  is the local branch name you are wanting to push

Or to pull a specific branch:

> git pull  

This tries to pull updates for the given branch based on its locally set 
upstream branch, git branch -vv shows details of your local branches and their 
corresponding remotes:

> git branch -vv
  JENA-1405   5937830 [rvesse/JENA-1405] Use better logging approach 
(JENA-1405)
  JENA-1407   9e2b4ce [rvesse/JENA-1407: ahead 1] Change degree of test 
parallelism (JENA-1407)
  JENA-1434   8df3702 [rvesse/JENA-1434] Minor fixes to new code (JENA-1434)
  JENA-1486   0eeb40d [rvesse/JENA-1486] Make sure to use datasets 
transactionally (JENA-1486)
  JENA-1497   44683c4 [rvesse/JENA-1497] Rename test cases and fix warnings 
(JENA-1497)
  JENA-50777a69f1 [origin/JENA-507: gone] Merge branch 'master' into 
JENA-507
  JENA-541cbc2dc2 Initial work on custom headers for SPARQL Updates 
(JENA-541)
  JENA-8933ab3138 More experimentation with splitting BZip2 inputs
  jena-db-testing 10441d7 [afs/jena-db-testing] Check .delete() in beforeTest
  jena2   9bc5aa9 [origin/jena2] Yet more fixes and test cases for 
assignment inlining (JENA-780)
* master  2e732b4 [origin/master: behind 2] Merge branch 'JENA-1497'
  obfuscate   08bdbc3 [rvesse/obfuscate] Add naive obfuscation provider

Or:

> git fetch --all
> git pull /

And merging a specific remote branch:

> git fetch --all
> git merge /

Similarly to checkout a specific remote branch locally:

> git fetch --all
> git checkout -B  --track /

You just need to be a little careful about doing pull/push without being 
explicit about the target remote as otherwise you'll go to/from the default 
(usually origin) which may not always be desired

Rob

On 19/03/2018, 10:31, "Claude Warren"  wrote:

What process are you using to keep your working copy of Jena (assuming you
have a clone on github) from the true master copy of Jena such that you can
create pull requests from you copy and merge them into the master.

So far the only way I have found to do this is to keep 2 copies of the code
in 2 different local git repositories.  the first I pull from master,
update, test, etc. check into my version on github, generate a pull request
from there.

The second is the master from apache git where I pull the code down, and
perform the merge from my github version.

Is there another way to do this?

Claude

-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

[jira] [Commented] (JENA-1509) RDFConnectionRemote does not execute update( UpdateRequest )

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404610#comment-16404610
 ] 

ASF GitHub Bot commented on JENA-1509:
--

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/387#discussion_r175388799
  
--- Diff: 
jena-rdfconnection/src/main/java/org/apache/jena/rdfconnection/RDFConnectionRemote.java
 ---
@@ -280,7 +280,7 @@ private void updateExec(UpdateRequest update, String 
updateString ) {
 }
 // Use the query string as provided if possible, otherwise 
serialize the query.
--- End diff --

s/query/update/g


> RDFConnectionRemote does not execute update( UpdateRequest )
> 
>
> Key: JENA-1509
> URL: https://issues.apache.org/jira/browse/JENA-1509
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.7.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Major
>
> If an UpdateRequest is constructed and passed to the 
> RDFConnectionRemote.update() method the string value is lost and the results 
> is an "update string may not be null" exception.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] jena pull request #387: fix for JENA-1509

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/387#discussion_r175388799
  
--- Diff: 
jena-rdfconnection/src/main/java/org/apache/jena/rdfconnection/RDFConnectionRemote.java
 ---
@@ -280,7 +280,7 @@ private void updateExec(UpdateRequest update, String 
updateString ) {
 }
 // Use the query string as provided if possible, otherwise 
serialize the query.
--- End diff --

s/query/update/g


---

number of git clones?

[Claude Warren]

What process are you using to keep your working copy of Jena (assuming you
have a clone on github) from the true master copy of Jena such that you can
create pull requests from you copy and merge them into the master.

So far the only way I have found to do this is to keep 2 copies of the code
in 2 different local git repositories.  the first I pull from master,
update, test, etc. check into my version on github, generate a pull request
from there.

The second is the master from apache git where I pull the code down, and
perform the merge from my github version.

Is there another way to do this?

Claude

-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

[jira] [Commented] (JENA-1509) RDFConnectionRemote does not execute update( UpdateRequest )

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404586#comment-16404586
 ] 

ASF GitHub Bot commented on JENA-1509:
--

GitHub user Claudenw opened a pull request:

https://github.com/apache/jena/pull/387

fix for JENA-1509

fixed string issue and added tests

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Claudenw/jena master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/387.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #387


commit 3604ddff2d7465205f3935391862df1bac681a30
Author: Claude Warren 
Date:   2018-03-19T10:13:08Z

fix for JENA-1509




> RDFConnectionRemote does not execute update( UpdateRequest )
> 
>
> Key: JENA-1509
> URL: https://issues.apache.org/jira/browse/JENA-1509
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.7.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Major
>
> If an UpdateRequest is constructed and passed to the 
> RDFConnectionRemote.update() method the string value is lost and the results 
> is an "update string may not be null" exception.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] jena pull request #387: fix for JENA-1509

[Claudenw]

GitHub user Claudenw opened a pull request:

https://github.com/apache/jena/pull/387

fix for JENA-1509

fixed string issue and added tests

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Claudenw/jena master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/387.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #387


commit 3604ddff2d7465205f3935391862df1bac681a30
Author: Claude Warren 
Date:   2018-03-19T10:13:08Z

fix for JENA-1509




---

[jira] [Assigned] (JENA-1509) RDFConnectionRemote does not execute update( UpdateRequest )

[Claude Warren (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claude Warren reassigned JENA-1509:
---

Assignee: Claude Warren

> RDFConnectionRemote does not execute update( UpdateRequest )
> 
>
> Key: JENA-1509
> URL: https://issues.apache.org/jira/browse/JENA-1509
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Jena
>Affects Versions: Jena 3.7.0
>Reporter: Claude Warren
>Assignee: Claude Warren
>Priority: Major
>
> If an UpdateRequest is constructed and passed to the 
> RDFConnectionRemote.update() method the string value is lost and the results 
> is an "update string may not be null" exception.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (JENA-1509) RDFConnectionRemote does not execute update( UpdateRequest )

[Claude Warren (JIRA)]

Claude Warren created JENA-1509:
---

 Summary: RDFConnectionRemote does not execute update( 
UpdateRequest )
 Key: JENA-1509
 URL: https://issues.apache.org/jira/browse/JENA-1509
 Project: Apache Jena
  Issue Type: Bug
  Components: Jena
Affects Versions: Jena 3.7.0
Reporter: Claude Warren


If an UpdateRequest is constructed and passed to the 
RDFConnectionRemote.update() method the string value is lost and the results is 
an "update string may not be null" exception.

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)