November 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-592) Filtering situations by status "Unresolved" is not working

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-592?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-592. ------------------------------ Resolution: Done > Filtering situations by status "Unresolved" is not working > ---------------------------------------------------------- > > Key: RTGOV-592 > URL: https://issues.jboss.org/browse/RTGOV-592 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: Fuse 6.1 + switchyard 2.0.0.Alpha3 + overlord 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Filtering by status "Unresolved" always return No situations found. even if there are unresolved situations. All other statuses (resolved, in progress..) are working correctly -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-592) Filtering situations by status "Unresolved" is not working

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-592?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-592: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/241 > Filtering situations by status "Unresolved" is not working > ---------------------------------------------------------- > > Key: RTGOV-592 > URL: https://issues.jboss.org/browse/RTGOV-592 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: Fuse 6.1 + switchyard 2.0.0.Alpha3 + overlord 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Filtering by status "Unresolved" always return No situations found. even if there are unresolved situations. All other statuses (resolved, in progress..) are working correctly -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-531?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-531: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/511 > Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side > --------------------------------------------------------------------------- > > Key: SRAMP-531 > URL: https://issues.jboss.org/browse/SRAMP-531 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See: > - shell's UploadArtifactCommand and DeployCommand > - ui's ArtifactUploadServlet > - wagon's SrampWagon > - server's Maven facade (MavenRepositoryServiceImpl) > Consider moving the expansion somewhere central and server-side. > If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-580) Server-side autodetection of artifact types

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-580?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-580: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/511 > Server-side autodetection of artifact types > ------------------------------------------- > > Key: SRAMP-580 > URL: https://issues.jboss.org/browse/SRAMP-580 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, artifact type autodetection exists in multiple forms, nearly all of them client-side. The Maven Wagon inspects the deployment URL and makes assumptions. The UI checks file extensions. > Instead, move a more complete set of artifact-inspection logic server-side. Some semblance of this already exists, to a certain degree. For example, ZipToSrampArchiveProvider#accept(ArtifactType) already exists, but is currently used only to determine which module should expand the artifact. But, the concept could be used to define the artifact type based on the new artifact. It would require a hierarchy of sorts where the most "specialized" integrations (Switchyard, RTGov, DTGov, etc.) are considered first. If none of those "accept" the artifact, the next tier (more generic types) are considered. > The logic could be a mix of filename regex, archive inspection (ex: look for switchyard.xml), etc. > This should completely replace all other types of client-side logic. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() not persisted

by Lukas Krejci (JIRA)

[ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.... ] Lukas Krejci updated SRAMP-622: ------------------------------- Attachment: reproducer.zip A simple maven project to reproduce the issue. Run: mvn package exec:java -Dexec.mainClass=SrampCustomAttributesMissingReproducer -Dexec.args="http://localhost:8080/s-ramp-server s-ramp s-ramp" where the first arg is the S-RAMP server endpoint, the second is user name and the third is the password. > Relationship.getOtherAttributes() not persisted > ----------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() not persisted

by Lukas Krejci (JIRA)

Lukas Krejci created SRAMP-622: ---------------------------------- Summary: Relationship.getOtherAttributes() not persisted Key: SRAMP-622 URL: https://issues.jboss.org/browse/SRAMP-622 Project: S-RAMP Issue Type: Bug Components: Persistence Affects Versions: 0.7.0.Final Reporter: Lukas Krejci Assignee: Brett Meyer The API allows for the relationships to have arbitrary "other" attributes on them. These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-615) Reimplement export situations functionality in RTGov UI

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-615?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-615. ------------------------------ Resolution: Done > Reimplement export situations functionality in RTGov UI > ------------------------------------------------------- > > Key: RTGOV-615 > URL: https://issues.jboss.org/browse/RTGOV-615 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Current approach disabled as used Errai bus. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-615) Reimplement export situations functionality in RTGov UI

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-615?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-615: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/240 > Reimplement export situations functionality in RTGov UI > ------------------------------------------------------- > > Key: RTGOV-615 > URL: https://issues.jboss.org/browse/RTGOV-615 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Current approach disabled as used Errai bus. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-612) Assigning situation and changing states produces new call traces

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-612?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-612: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/239 > Assigning situation and changing states produces new call traces > ---------------------------------------------------------------- > > Key: RTGOV-612 > URL: https://issues.jboss.org/browse/RTGOV-612 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: eap 6.3 + sy 2 + rtgov 2.0 Final > Reporter: Andrej Vano > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Final > > > Assigning situation and changing states produces new non-persistent call traces in the call trace window -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (RTGOV-612) Assigning situation and changing states produces new call traces

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-612?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-612. ------------------------------ Resolution: Done > Assigning situation and changing states produces new call traces > ---------------------------------------------------------------- > > Key: RTGOV-612 > URL: https://issues.jboss.org/browse/RTGOV-612 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: eap 6.3 + sy 2 + rtgov 2.0 Final > Reporter: Andrej Vano > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Final > > > Assigning situation and changing states produces new non-persistent call traces in the call trace window -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues November 2014