February 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-400) Shell 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 was:When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user. > Shell 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 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[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: ------------------------------ Summary: Client requests missing providers for most Exceptions (was: Shell missing providers for most Exceptions) > 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 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-400) Shell 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: ------------------------------ Summary: Shell missing providers for most Exceptions (was: S-RAMP Shell Ontology Exception when upload existing ontology) > Shell 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 > > When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-421) S-ramp shell UploadArtifactCommand Add name and description

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-421?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-421. ----------------------------- Resolution: Out of Date > S-ramp shell UploadArtifactCommand Add name and description > ----------------------------------------------------------- > > Key: ARTIF-421 > URL: https://issues.jboss.org/browse/ARTIF-421 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-645: ---------------------------------- *Requirements currently not being considered:* * Represent situations in a tree representing the resubmission failures {quote} This is not being considered, as it assume resubmission failures are the primary focus of the visual representation - whereas in most situations resubmission will not be used. Therefore instead, the situation list will remain and a means of navigating the tree will be provided on the situation details page. {quote} * The root node shows the number of resubmits so far (this is equal to the number of child nodes). {quote} Not sure of the benefit of this? One resubmission may result in two or more situations being created - counting nodes would then return an incorrect value. Resubmission count would be more to do with the depth of the tree. {quote} *Requirements and Questions:* * Only the newest situation in a tree is allowed to be resubmitted. {quote} Does this mean that situations that don't have any linked (child) situations can be resubmitted any number of times, or should a situation only be able to be resubmitted once, regardless of success or fail? {quote} * Filter criteria in the Situations tab apply only to root situations. If a child situation would match the criteria, but the root situation does not, the whole tree is hidden. This means that a tree is never shown partially. Either the tree is fully shown or hidden. [This is a simplification, even though it may leave the user wanting more] {quote} As discussed above, the use of a tree is not appropriate for a majority of rtgov UI usage. Another option may be to only show (and filter) the situations that are effectively leaf nodes? If needing to access the intermediate or root nodes, then these could be done through navigating from the leaf nodes? {quote} * Applying a bulk action on the Situations tab: a) "Retry" and "Export" are applied only to the newest situation of the selected trees. {quote} This would fit with the suggested approach above of only listing 'leaf' situations. {quote} b) "Delete" is applied to all situations of the selected trees. Thus, it deletes the whole tree. * The "assignedTo" and "resolutionState" properties apply to the whole tree. Whenever these properties are changed for a situation, the change is propagated to all situations in the tree. When a child situation is created, these properties shall be set according to the root situation's properties. > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-398) S-RAMP Shell Add Alias parsing in non interactive mode

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-398?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-398. ----------------------------- Resolution: Out of Date > S-RAMP Shell Add Alias parsing in non interactive mode > ------------------------------------------------------ > > Key: ARTIF-398 > URL: https://issues.jboss.org/browse/ARTIF-398 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > When no interactive mode is selected, for example in the file mode (-f) the alias file is not getting processed. > It is not possible to pass to Aesh Parser a Setting object that contains the alias file, so the solution would be to parse manually the alias file and substitute the alias by the original command name. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-398) S-RAMP Shell Add Alias parsing in non interactive mode

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-398?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-398: ----------------------------------- Aesh 0.5x now handles aliases in the batch files correctly. > S-RAMP Shell Add Alias parsing in non interactive mode > ------------------------------------------------------ > > Key: ARTIF-398 > URL: https://issues.jboss.org/browse/ARTIF-398 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > When no interactive mode is selected, for example in the file mode (-f) the alias file is not getting processed. > It is not possible to pass to Aesh Parser a Setting object that contains the alias file, so the solution would be to parse manually the alias file and substitute the alias by the original command name. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-572) S-RAMP Username should not be added to the CLI history

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-572?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-572. ----------------------------- Resolution: Out of Date > S-RAMP Username should not be added to the CLI history > ------------------------------------------------------ > > Key: ARTIF-572 > URL: https://issues.jboss.org/browse/ARTIF-572 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Minor > > How to reproduce: > 1.) Start up s-ramp-shell > 2.) connect http://localhost:8080/s-ramp-server > 3.) enter username and password > 4.) hit the up-arrow key > 5.) note that the username provided in #3 appears in the history > *No* user-provided values should be in the history. Find out why that's getting added. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-572) S-RAMP Username should not be added to the CLI history

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-572?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-572: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Bug) > S-RAMP Username should not be added to the CLI history > ------------------------------------------------------ > > Key: ARTIF-572 > URL: https://issues.jboss.org/browse/ARTIF-572 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Minor > > How to reproduce: > 1.) Start up s-ramp-shell > 2.) connect http://localhost:8080/s-ramp-server > 3.) enter username and password > 4.) hit the up-arrow key > 5.) note that the username provided in #3 appears in the history > *No* user-provided values should be in the history. Find out why that's getting added. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-573: ----------------------------------- May be resolved by AESH-309 > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2015