[jira] [Issue Comment Deleted] (JENA-1114) sparql tool help and documentation should be more specific about --data and --query formating parameters

["Ramiro Pereira de Magalhães (JIRA)" <ji...@apache.org>]

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

Ramiro Pereira de Magalhães updated JENA-1114:
----------------------------------------------
    Comment: was deleted

(was: Sure. Just wait a couple days then I'll be able to provide some more information to you. I must say though it didn't help me much, because the exception wasn't thrown where it happened. The errors were collected while the thread was running in a method then thrown from another method after the other one was completed. Turning debug on didn't reveal much information also.)

> sparql tool help and documentation should be more specific about --data and --query formating parameters
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JENA-1114
>                 URL: https://issues.apache.org/jira/browse/JENA-1114
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Cmd line tools, Documentation
>    Affects Versions: Jena 3.0.1
>         Environment: Windows 7
>            Reporter: Ramiro Pereira de Magalhães
>              Labels: documentation
>
> In Windows, the sparql tool's options {{\-\-data}} and {{\-\-query}} must be formated as an URI, or it throws a "Code: 4/UNWISE_CHARACTER in PATH" exception. It took me quite some time to notice that, and probably I would have lost much less time figuring this out if the {{\-\-help}} was explicit about this. The same also applies to the [documentation|https://jena.apache.org/documentation/query/cmds.html]. It seems this confusion happens with [other users too|http://mail-archives.apache.org/mod_mbox/jena-users/201209.mbox/%3C504E4D07.6080803@apache.org%3E].
> Therefore, I suggest that both the command line help and the documentation be updated to be a more specific about this requirement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)