June 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-160) Change artifact's 'delete' action to be a logical delete

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-160?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-160. ------------------------------- > Change artifact's 'delete' action to be a logical delete > -------------------------------------------------------- > > Key: SRAMP-160 > URL: https://issues.jboss.org/browse/SRAMP-160 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The reason for doing this is that we should not allow duplicate UUIDs, even for deleted artifacts. Currently a delete will remove the artifact from the repository. Instead, we should either move the artifact to some alternate collection or simply tag it as deleted (and then augment all incoming queries with a predicate that will exclude deleted artifacts). > Do we need a way to actually for-real delete an artifact? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-160) Change artifact's 'delete' action to be a logical delete

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-160?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-160. --------------------------------- Resolution: Done Changed artifact delete to be a logical rather than a hard delete. The artifact JCR node is now stripped of its sramp mixin type and moved from /s-ramp/ to /s-ramp-trash/. The move isn't strictly necessary but it was an easy way to make sure getArtifact wouldn't be able to find it. > Change artifact's 'delete' action to be a logical delete > -------------------------------------------------------- > > Key: SRAMP-160 > URL: https://issues.jboss.org/browse/SRAMP-160 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The reason for doing this is that we should not allow duplicate UUIDs, even for deleted artifacts. Currently a delete will remove the artifact from the repository. Instead, we should either move the artifact to some alternate collection or simply tag it as deleted (and then augment all incoming queries with a predicate that will exclude deleted artifacts). > Do we need a way to actually for-real delete an artifact? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-160) Change artifact's 'delete' action to be a logical delete

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-160?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-160: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/266 > Change artifact's 'delete' action to be a logical delete > -------------------------------------------------------- > > Key: SRAMP-160 > URL: https://issues.jboss.org/browse/SRAMP-160 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The reason for doing this is that we should not allow duplicate UUIDs, even for deleted artifacts. Currently a delete will remove the artifact from the repository. Instead, we should either move the artifact to some alternate collection or simply tag it as deleted (and then augment all incoming queries with a predicate that will exclude deleted artifacts). > Do we need a way to actually for-real delete an artifact? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-211) Update order mgmt app quickstart description to explain handler and auditor

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-211?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-211. ------------------------------ Fix Version/s: (was: 1.0.0.Final) Resolution: Rejected Docs already sufficiently describe the use of the auditor and handler switchyard mechanisms. > Update order mgmt app quickstart description to explain handler and auditor > --------------------------------------------------------------------------- > > Key: RTGOV-211 > URL: https://issues.jboss.org/browse/RTGOV-211 > Project: RTGov (Run Time Governance) > Issue Type: Task > Components: Documentation > Reporter: Gary Brown > Assignee: Gary Brown > > The latest release now uses an event listener to get the activity events from switchyard, but the quickstart uses both a handler and auditor in support of different demo'd capabilities. > Need to update the docs to clearly explain how these are being used. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-212) Document database configuration

by Gary Brown (JIRA)

Gary Brown created RTGOV-212: -------------------------------- Summary: Document database configuration Key: RTGOV-212 URL: https://issues.jboss.org/browse/RTGOV-212 Project: RTGov (Run Time Governance) Issue Type: Task Components: Documentation Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-211) Update order mgmt app quickstart description to explain handler and auditor

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-211?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-211: ----------------------------- Fix Version/s: 1.0.0.Final (was: 1.0.0.M5) > Update order mgmt app quickstart description to explain handler and auditor > --------------------------------------------------------------------------- > > Key: RTGOV-211 > URL: https://issues.jboss.org/browse/RTGOV-211 > Project: RTGov (Run Time Governance) > Issue Type: Task > Components: Documentation > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.Final > > > The latest release now uses an event listener to get the activity events from switchyard, but the quickstart uses both a handler and auditor in support of different demo'd capabilities. > Need to update the docs to clearly explain how these are being used. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-160) Change artifact's 'delete' action to be a logical delete

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-160?page=com.atlassian.jira.plugin.... ] Work on SRAMP-160 started by Eric Wittmann. > Change artifact's 'delete' action to be a logical delete > -------------------------------------------------------- > > Key: SRAMP-160 > URL: https://issues.jboss.org/browse/SRAMP-160 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The reason for doing this is that we should not allow duplicate UUIDs, even for deleted artifacts. Currently a delete will remove the artifact from the repository. Instead, we should either move the artifact to some alternate collection or simply tag it as deleted (and then augment all incoming queries with a predicate that will exclude deleted artifacts). > Do we need a way to actually for-real delete an artifact? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-71) Hide Download Content link for non-Document artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-71?page=com.atlassian.jira.plugin... ] Eric Wittmann updated SRAMPUI-71: --------------------------------- Git Pull Request: https://github.com/Governance/s-ramp-ui/pull/73 > Hide Download Content link for non-Document artifacts > ----------------------------------------------------- > > Key: SRAMPUI-71 > URL: https://issues.jboss.org/browse/SRAMPUI-71 > Project: S-RAMP UI > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 > > > If an artifact has no file content, then the Download Content link should not appear. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-71) Hide Download Content link for non-Document artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-71?page=com.atlassian.jira.plugin... ] Eric Wittmann closed SRAMPUI-71. -------------------------------- > Hide Download Content link for non-Document artifacts > ----------------------------------------------------- > > Key: SRAMPUI-71 > URL: https://issues.jboss.org/browse/SRAMPUI-71 > Project: S-RAMP UI > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 > > > If an artifact has no file content, then the Download Content link should not appear. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-71) Hide Download Content link for non-Document artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-71?page=com.atlassian.jira.plugin... ] Eric Wittmann resolved SRAMPUI-71. ---------------------------------- Resolution: Done > Hide Download Content link for non-Document artifacts > ----------------------------------------------------- > > Key: SRAMPUI-71 > URL: https://issues.jboss.org/browse/SRAMPUI-71 > Project: S-RAMP UI > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 > > > If an artifact has no file content, then the Download Content link should not appear. -- 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, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2013