June 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-476) Lazy-load of JCR repository incompatible with maven repo facade auth

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-476?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-476. ------------------------------- > Lazy-load of JCR repository incompatible with maven repo facade auth > -------------------------------------------------------------------- > > Key: SRAMP-476 > URL: https://issues.jboss.org/browse/SRAMP-476 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > The maven repository facade authentication will create a read-only user for accessing the repository. However, we are lazy-loading the JCR repository. So if the read-only maven repository facade credentials are used for the very first request to s-ramp, then jcr repo creation will fail. > The solution is to no longer lazy-load the repository. Instead, fabricate an admin-rights user on startup of the s-ramp WAR and use that to create the repository in a separate thread. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-478) NPE when retrieving situation list from rtgov-ui in FSW 6.0

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-478?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-478. ------------------------------ Resolution: Done Thanks for the pointer Michael. > NPE when retrieving situation list from rtgov-ui in FSW 6.0 > ----------------------------------------------------------- > > Key: RTGOV-478 > URL: https://issues.jboss.org/browse/RTGOV-478 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > When deploying the rtgov-ui to FSW 6.0 (war found in the ui/overlord-rtgov-ui-war-fsw60 module, accessing the situations page shows a null pointer exception in a popup window. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-498) EPN for reporting responsetime events to Elasticsearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-498?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-498: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/121 > EPN for reporting responsetime events to Elasticsearch > ------------------------------------------------------ > > Key: RTGOV-498 > URL: https://issues.jboss.org/browse/RTGOV-498 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Elasticsearch is only available as part of the new RTGov UI that can be deployed as a separate component on FSW 6.0. > Therefore this task will provide an EPN that will subscribe to the responsetime events and persist them in Elasticsearch. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-498) EPN for reporting responsetime events to Elasticsearch

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-498?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-498. ------------------------------ Resolution: Done > EPN for reporting responsetime events to Elasticsearch > ------------------------------------------------------ > > Key: RTGOV-498 > URL: https://issues.jboss.org/browse/RTGOV-498 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Elasticsearch is only available as part of the new RTGov UI that can be deployed as a separate component on FSW 6.0. > Therefore this task will provide an EPN that will subscribe to the responsetime events and persist them in Elasticsearch. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-478) NPE when retrieving situation list from rtgov-ui in FSW 6.0

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-478?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-478: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/121 > NPE when retrieving situation list from rtgov-ui in FSW 6.0 > ----------------------------------------------------------- > > Key: RTGOV-478 > URL: https://issues.jboss.org/browse/RTGOV-478 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > When deploying the rtgov-ui to FSW 6.0 (war found in the ui/overlord-rtgov-ui-war-fsw60 module, accessing the situations page shows a null pointer exception in a popup window. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-476) Lazy-load of JCR repository incompatible with maven repo facade auth

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-476?page=com.atlassian.jira.plugin.... ] Work on SRAMP-476 started by Eric Wittmann. > Lazy-load of JCR repository incompatible with maven repo facade auth > -------------------------------------------------------------------- > > Key: SRAMP-476 > URL: https://issues.jboss.org/browse/SRAMP-476 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > The maven repository facade authentication will create a read-only user for accessing the repository. However, we are lazy-loading the JCR repository. So if the read-only maven repository facade credentials are used for the very first request to s-ramp, then jcr repo creation will fail. > The solution is to no longer lazy-load the repository. Instead, fabricate an admin-rights user on startup of the s-ramp WAR and use that to create the repository in a separate thread. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-476) Lazy-load of JCR repository incompatible with maven repo facade auth

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-476: ----------------------------------- Summary: Lazy-load of JCR repository incompatible with maven repo facade auth Key: SRAMP-476 URL: https://issues.jboss.org/browse/SRAMP-476 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.5.0.Final The maven repository facade authentication will create a read-only user for accessing the repository. However, we are lazy-loading the JCR repository. So if the read-only maven repository facade credentials are used for the very first request to s-ramp, then jcr repo creation will fail. The solution is to no longer lazy-load the repository. Instead, fabricate an admin-rights user on startup of the s-ramp WAR and use that to create the repository in a separate thread. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-475) Remove JAXBContext trickery from s-ramp atom utils

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-475: ----------------------------------- Summary: Remove JAXBContext trickery from s-ramp atom utils Key: SRAMP-475 URL: https://issues.jboss.org/browse/SRAMP-475 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Components: Core Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.6.0 There is currently an issue in RE where the JAXBContextFinder is not set on Entry objects inside an Atom Feed. This is a problem with the Feed unmarshaller. Once that is fixed in RE, we can remove the following method from s-ramp: SrampAtomUtils::setFinder() -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-500) Failed to get message for activity type id 'org.overlord.rtgov.activity.model.ActivityTypeId@....'

by Gary Brown (JIRA)

Gary Brown created RTGOV-500: -------------------------------- Summary: Failed to get message for activity type id 'org.overlord.rtgov.activity.model.ActivityTypeId@....' Key: RTGOV-500 URL: https://issues.jboss.org/browse/RTGOV-500 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final When deploying RTGov UI to FSW6.0, it is now possible to get the list of situations (after RTGOV-478 was fixed) but selecting a situation causes the error: Failed to get message for activity type id 'org.overlord.rtgov.activity.model.ActivityTypeId@......'. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-499) Change to use getSituationProperties when support for FSW60 no longer required

by Gary Brown (JIRA)

Gary Brown created RTGOV-499: -------------------------------- Summary: Change to use getSituationProperties when support for FSW60 no longer required Key: RTGOV-499 URL: https://issues.jboss.org/browse/RTGOV-499 Project: RTGov (Run Time Governance) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Currently using the deprecated Situation.getProperties method in a few places. This is to enable support for deploying the new RTGov UI, and an EPN for recording response time events in Elasticsearch, within FSW60. Once this support is no longer required, these should be changed to use the getSituationProperties method. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014