[ https://issues.apache.org/jira/browse/JENA-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504813#comment-17504813 ]
Richard Cyganiak commented on JENA-2293: ---------------------------------------- I have verified that this indeed fixes the issue in our product. Thank you! I see that the new test cases in TestUpdateSilent already cover a couple of similar cases that I meant to investigate further. That saves me the work. Thank you once again! > SPARQL Update: DatasetGraphOne: NPE when COPY or MOVE to named graph > -------------------------------------------------------------------- > > Key: JENA-2293 > URL: https://issues.apache.org/jira/browse/JENA-2293 > Project: Apache Jena > Issue Type: Bug > Affects Versions: Jena 4.4.0 > Reporter: Richard Cyganiak > Assignee: Andy Seaborne > Priority: Major > Fix For: Jena 4.5.0 > > Attachments: SPARQLUpdateTest.java > > > When executing SPARQL Update requests against a dataset that does not > automatically create new graphs, COPY or MOVE operations with a non-existing > graph as the target will result in a NullPointerException. The same happens > when adding SILENT. > I would expect these requests to result in UpdateExceptions, with a message > pointing out the non-existing graph. Or nothing in the case of SILENT. > The attached JUnit 4 test demonstrates this by running queries against a > DatasetGraphOne: > COPY DEFAULT TO <http://example.org/no-such-graph> > COPY SILENT DEFAULT TO <http://example.org/no-such-graph> > MOVE DEFAULT TO <http://example.org/no-such-graph> > MOVE SILENT DEFAULT TO <http://example.org/no-such-graph> > Each request produces an NPE. -- This message was sent by Atlassian Jira (v8.20.1#820001)