[JBoss JIRA] (ARTIF-402) S-RAMP Shell New Commands
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-402?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-402:
------------------------------
Description:
Some new commands to be added:
- s-ramp:clear: clean the current s-ramp session.
- ontology:status: will work as the s-ramp:status command, but it applies to ontology.
was:
Some new commands to be added:
- s-ramp:clear: clean the current s-ramp session.
- ontology:status: will work as the s-ramp:status command, but it applies to ontology.
- storedQuery:status: ditto
> S-RAMP Shell New Commands
> -------------------------
>
> Key: ARTIF-402
> URL: https://issues.jboss.org/browse/ARTIF-402
> Project: Artificer
> Issue Type: Sub-task
> Reporter: David virgil naranjo
> Assignee: Brett Meyer
>
> Some new commands to be added:
> - s-ramp:clear: clean the current s-ramp session.
> - ontology:status: will work as the s-ramp:status command, but it applies to ontology.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ARTIF-402) S-RAMP Shell New Commands
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-402?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-402:
------------------------------
Description:
Some new commands to be added:
- s-ramp:clear: clean the current s-ramp session.
- ontology:status: will work as the s-ramp:status command, but it applies to ontology.
- storedQuery:status: ditto
was:
Some new commands to be added:
- s-ramp:clear: clean the current s-ramp session.
- ontology:status: will work as the s-ramp:status command, but it applies to ontology.
> S-RAMP Shell New Commands
> -------------------------
>
> Key: ARTIF-402
> URL: https://issues.jboss.org/browse/ARTIF-402
> Project: Artificer
> Issue Type: Sub-task
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> Some new commands to be added:
> - s-ramp:clear: clean the current s-ramp session.
> - ontology:status: will work as the s-ramp:status command, but it applies to ontology.
> - storedQuery:status: ditto
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.... ]
Brett Meyer reassigned ARTIF-400:
---------------------------------
Assignee: Brett Meyer (was: David virgil naranjo)
> Client requests missing providers for most Exceptions
> -----------------------------------------------------
>
> Key: ARTIF-400
> URL: https://issues.jboss.org/browse/ARTIF-400
> Project: Artificer
> Issue Type: Sub-task
> Reporter: David virgil naranjo
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> This task started out as:
> {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote}
> However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved ARTIF-400.
-------------------------------
Fix Version/s: 1.0.0.Alpha1
Resolution: Done
> Client requests missing providers for most Exceptions
> -----------------------------------------------------
>
> Key: ARTIF-400
> URL: https://issues.jboss.org/browse/ARTIF-400
> Project: Artificer
> Issue Type: Sub-task
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
> Fix For: 1.0.0.Alpha1
>
>
> This task started out as:
> {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote}
> However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-400:
------------------------------
Description:
This task started out as:
{quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote}
However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests.
was:
This task started out as:
{quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote}
However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up
> Client requests missing providers for most Exceptions
> -----------------------------------------------------
>
> Key: ARTIF-400
> URL: https://issues.jboss.org/browse/ARTIF-400
> Project: Artificer
> Issue Type: Sub-task
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> This task started out as:
> {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote}
> However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months