August 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-251) MVEL information transformer returns null if value is not a string

by Gary Brown (JIRA)

Gary Brown created RTGOV-251: -------------------------------- Summary: MVEL information transformer returns null if value is not a string Key: RTGOV-251 URL: https://issues.jboss.org/browse/RTGOV-251 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.1.0.Final Should return the 'toString' value instead. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-157) Implement Auditing in the S-RAMP repository

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-157?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-157. --------------------------------- Resolution: Done > Implement Auditing in the S-RAMP repository > ------------------------------------------- > > Key: SRAMP-157 > URL: https://issues.jboss.org/browse/SRAMP-157 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.1 - jBPM - bugfix 1 > > > We want to make sure that we have full auditing support so that we can track all changes made to artifacts. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-157) Implement Auditing in the S-RAMP repository

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-157?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-157. ------------------------------- > Implement Auditing in the S-RAMP repository > ------------------------------------------- > > Key: SRAMP-157 > URL: https://issues.jboss.org/browse/SRAMP-157 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.1 - jBPM - bugfix 1 > > > We want to make sure that we have full auditing support so that we can track all changes made to artifacts. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-216) CLI should fail on command error when in batch mode

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-216?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-216: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/302 > CLI should fail on command error when in batch mode > --------------------------------------------------- > > Key: SRAMP-216 > URL: https://issues.jboss.org/browse/SRAMP-216 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The S-RAMP CLI should fail with an appropriate command-line error code if a command in the list fails. This should only happen when running in batch mode. In interactive mode it should just print out the error message and return to the prompt. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-216) CLI should fail on command error when in batch mode

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-216?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-216. --------------------------------- Resolution: Done Commands now return a boolean from "execute". The command runner bails with a System.exit(1) if a command return false *and* the runner is in batch mode. > CLI should fail on command error when in batch mode > --------------------------------------------------- > > Key: SRAMP-216 > URL: https://issues.jboss.org/browse/SRAMP-216 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The S-RAMP CLI should fail with an appropriate command-line error code if a command in the list fails. This should only happen when running in batch mode. In interactive mode it should just print out the error message and return to the prompt. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-216) CLI should fail on command error when in batch mode

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-216?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-216. ------------------------------- > CLI should fail on command error when in batch mode > --------------------------------------------------- > > Key: SRAMP-216 > URL: https://issues.jboss.org/browse/SRAMP-216 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The S-RAMP CLI should fail with an appropriate command-line error code if a command in the list fails. This should only happen when running in batch mode. In interactive mode it should just print out the error message and return to the prompt. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-216) CLI should fail on command error when in batch mode

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-216?page=com.atlassian.jira.plugin.... ] Work on SRAMP-216 started by Eric Wittmann. > CLI should fail on command error when in batch mode > --------------------------------------------------- > > Key: SRAMP-216 > URL: https://issues.jboss.org/browse/SRAMP-216 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > The S-RAMP CLI should fail with an appropriate command-line error code if a command in the list fails. This should only happen when running in batch mode. In interactive mode it should just print out the error message and return to the prompt. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-197) Auditing: re-implement *not* using JCR observer pattern

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-197?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-197. ------------------------------- > Auditing: re-implement *not* using JCR observer pattern > ------------------------------------------------------- > > Key: SRAMP-197 > URL: https://issues.jboss.org/browse/SRAMP-197 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.2.0 - Security & S-RAMP-1.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.1 - jBPM - bugfix 1 > > > Re-write the core auditing to no longer use the JCR observer pattern. The JCR observer pattern introduces a number of challenges, including: > 1) async processing of auditing information. this is problematic in a number of ways, but most importantly is that data may be lost due to slower processing of the auditing information than the information on the artifact itself. Since the JCR observation events don't contain before and/or after values for changes, we have to go after the data directly. If changes happen quickly (before the observer has a crack at it) then data may be lost. > 2) multi-phase processing of artifact adds/updates in the jcrpersistence impl -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-197) Auditing: re-implement *not* using JCR observer pattern

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-197?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-197: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/301 > Auditing: re-implement *not* using JCR observer pattern > ------------------------------------------------------- > > Key: SRAMP-197 > URL: https://issues.jboss.org/browse/SRAMP-197 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.2.0 - Security & S-RAMP-1.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.1 - jBPM - bugfix 1 > > > Re-write the core auditing to no longer use the JCR observer pattern. The JCR observer pattern introduces a number of challenges, including: > 1) async processing of auditing information. this is problematic in a number of ways, but most importantly is that data may be lost due to slower processing of the auditing information than the information on the artifact itself. Since the JCR observation events don't contain before and/or after values for changes, we have to go after the data directly. If changes happen quickly (before the observer has a crack at it) then data may be lost. > 2) multi-phase processing of artifact adds/updates in the jcrpersistence impl -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-197) Auditing: re-implement *not* using JCR observer pattern

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-197?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-197. --------------------------------- Resolution: Done Auditing now happens synchronously. > Auditing: re-implement *not* using JCR observer pattern > ------------------------------------------------------- > > Key: SRAMP-197 > URL: https://issues.jboss.org/browse/SRAMP-197 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.2.0 - Security & S-RAMP-1.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.1 - jBPM - bugfix 1 > > > Re-write the core auditing to no longer use the JCR observer pattern. The JCR observer pattern introduces a number of challenges, including: > 1) async processing of auditing information. this is problematic in a number of ways, but most importantly is that data may be lost due to slower processing of the auditing information than the information on the artifact itself. Since the JCR observation events don't contain before and/or after values for changes, we have to go after the data directly. If changes happen quickly (before the observer has a crack at it) then data may be lost. > 2) multi-phase processing of artifact adds/updates in the jcrpersistence impl -- 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

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues August 2013