December 2012 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-133) Interactive shell pluggable commands

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-133?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-133. ------------------------------- > Interactive shell pluggable commands > ------------------------------------ > > Key: SRAMP-133 > URL: https://issues.jboss.org/browse/SRAMP-133 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > The interactive shell should be able to pick up contributed commands and incorporate them into the command factory. These commands should live in their own JARs. > Once that's done, move the BRMS commands out of s-ramp-client and into their own JAR. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-133) Interactive shell pluggable commands

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-133?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-133: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/136, https://github.com/Governance/s-ramp-distro/pull/4 > Interactive shell pluggable commands > ------------------------------------ > > Key: SRAMP-133 > URL: https://issues.jboss.org/browse/SRAMP-133 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > The interactive shell should be able to pick up contributed commands and incorporate them into the command factory. These commands should live in their own JARs. > Once that's done, move the BRMS commands out of s-ramp-client and into their own JAR. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-133) Interactive shell pluggable commands

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-133?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-133. --------------------------------- Resolution: Done The interactive shell will pick up any commands contributed via the ShellCommandProvider java service (ServiceLoader). It will look on the current classpath and in any JARs configured via the ~/.s-ramp/commands.ini configuration file. > Interactive shell pluggable commands > ------------------------------------ > > Key: SRAMP-133 > URL: https://issues.jboss.org/browse/SRAMP-133 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > The interactive shell should be able to pick up contributed commands and incorporate them into the command factory. These commands should live in their own JARs. > Once that's done, move the BRMS commands out of s-ramp-client and into their own JAR. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-133) Interactive shell pluggable commands

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-133?page=com.atlassian.jira.plugin.... ] Work on SRAMP-133 started by Eric Wittmann. > Interactive shell pluggable commands > ------------------------------------ > > Key: SRAMP-133 > URL: https://issues.jboss.org/browse/SRAMP-133 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > The interactive shell should be able to pick up contributed commands and incorporate them into the command factory. These commands should live in their own JARs. > Once that's done, move the BRMS commands out of s-ramp-client and into their own JAR. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-124) stacktrace in the log when not found uuid

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-124?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-124. --------------------------------- Resolution: Done See SRAMP-129 for details of the resolution. > stacktrace in the log when not found uuid > ----------------------------------------- > > Key: SRAMP-124 > URL: https://issues.jboss.org/browse/SRAMP-124 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > When a uuid is not found we should not log an exception, but rather a message at the INFO level > 09:31:25,971 ERROR Error found updating artifact meta-data: 2e455ad3-a469-401b-abe1-d3e737192893 > java.lang.Exception: Relationship creation error - failed to find an s-ramp artifact with target UUID: not-a-valid-uuid > at org.overlord.sramp.repository.jcr.JCRPersistence$JCRReferenceFactoryImpl.createReference(JCRPersistence.java:766) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.setRelationships(ArtifactToJCRNodeVisitor.java:536) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-124) stacktrace in the log when not found uuid

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-124?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-124: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/134 > stacktrace in the log when not found uuid > ----------------------------------------- > > Key: SRAMP-124 > URL: https://issues.jboss.org/browse/SRAMP-124 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > When a uuid is not found we should not log an exception, but rather a message at the INFO level > 09:31:25,971 ERROR Error found updating artifact meta-data: 2e455ad3-a469-401b-abe1-d3e737192893 > java.lang.Exception: Relationship creation error - failed to find an s-ramp artifact with target UUID: not-a-valid-uuid > at org.overlord.sramp.repository.jcr.JCRPersistence$JCRReferenceFactoryImpl.createReference(JCRPersistence.java:766) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.setRelationships(ArtifactToJCRNodeVisitor.java:536) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-124) stacktrace in the log when not found uuid

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-124?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-124. ------------------------------- > stacktrace in the log when not found uuid > ----------------------------------------- > > Key: SRAMP-124 > URL: https://issues.jboss.org/browse/SRAMP-124 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > When a uuid is not found we should not log an exception, but rather a message at the INFO level > 09:31:25,971 ERROR Error found updating artifact meta-data: 2e455ad3-a469-401b-abe1-d3e737192893 > java.lang.Exception: Relationship creation error - failed to find an s-ramp artifact with target UUID: not-a-valid-uuid > at org.overlord.sramp.repository.jcr.JCRPersistence$JCRReferenceFactoryImpl.createReference(JCRPersistence.java:766) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.setRelationships(ArtifactToJCRNodeVisitor.java:536) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-129) Be more selective about what errors get logged by the server

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-129?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-129. --------------------------------- Resolution: Done Formalized the error handling a bit. Every exception thrown by the s-ramp server is now either a user exception or a server exception. All exceptions are returned to the client in the response, but only server exceptions are logged. > Be more selective about what errors get logged by the server > ------------------------------------------------------------ > > Key: SRAMP-129 > URL: https://issues.jboss.org/browse/SRAMP-129 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > There are a few stacktraces when running the test. We should change our code to make sure we don't show stack traces if there is no true exception. > In general, this means we should be able to tell the difference between a hard server error (ioexception, modeshape blew up exception, etc) and a "user" error (invalid s-ramp query syntax, uuid not found, etc). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-129) Be more selective about what errors get logged by the server

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-129?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-129. ------------------------------- > Be more selective about what errors get logged by the server > ------------------------------------------------------------ > > Key: SRAMP-129 > URL: https://issues.jboss.org/browse/SRAMP-129 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > There are a few stacktraces when running the test. We should change our code to make sure we don't show stack traces if there is no true exception. > In general, this means we should be able to tell the difference between a hard server error (ioexception, modeshape blew up exception, etc) and a "user" error (invalid s-ramp query syntax, uuid not found, etc). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-129) Be more selective about what errors get logged by the server

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-129?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-129: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/134 > Be more selective about what errors get logged by the server > ------------------------------------------------------------ > > Key: SRAMP-129 > URL: https://issues.jboss.org/browse/SRAMP-129 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > There are a few stacktraces when running the test. We should change our code to make sure we don't show stack traces if there is no true exception. > In general, this means we should be able to tell the difference between a hard server error (ioexception, modeshape blew up exception, etc) and a "user" error (invalid s-ramp query syntax, uuid not found, etc). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues December 2012