December 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-633?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-633. ------------------------------ Resolution: Done > Situation lifecycle buttons don't react properly on EAP > ------------------------------------------------------- > > Key: RTGOV-633 > URL: https://issues.jboss.org/browse/RTGOV-633 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. > Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-633?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-633: ---------------------------------- Fixed by changing PUT methods to POST. > Situation lifecycle buttons don't react properly on EAP > ------------------------------------------------------- > > Key: RTGOV-633 > URL: https://issues.jboss.org/browse/RTGOV-633 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. > Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-633) Situation lifecycle buttons don't react properly on EAP

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-633?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-633: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/254 > Situation lifecycle buttons don't react properly on EAP > ------------------------------------------------------- > > Key: RTGOV-633 > URL: https://issues.jboss.org/browse/RTGOV-633 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is selected, pressing the 'Assign' or other subsequent lifecycle buttons does not immediately react. They have to be pressed multiple times before they result in an action. > Its possible that the cause is the same as for RTGOV-632 (i.e. a bad request). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-632. ------------------------------ Resolution: Done Worked around KeyCloak/EAP issue by serializing the REST invocations from the RTGov UI - specifically found the issue when retrieving the initial service and situations lists. > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-632: ---------------------------------- KeyCloak issue reported as: https://issues.jboss.org/browse/KEYCLOAK-873 > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-632) Initial display of service list on EAP is empty

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-632?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-632: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/253 > Initial display of service list on EAP is empty > ----------------------------------------------- > > Key: RTGOV-632 > URL: https://issues.jboss.org/browse/RTGOV-632 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When navigating to the 'Services' page initially, the list of services is empty. > This is because the server is returning a 'Bad Request' (code 400) - but when a refresh is performed, the response is ok and shows the list of services. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-517) Support Wildfly

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-517?page=com.atlassian.jira.plugin.... ] Work on SRAMP-517 started by Brett Meyer. ----------------------------------------- > Support Wildfly > --------------- > > Key: SRAMP-517 > URL: https://issues.jboss.org/browse/SRAMP-517 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-629) Convert auth to Keycloak

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-629?page=com.atlassian.jira.plugin.... ] Work on SRAMP-629 started by Brett Meyer. ----------------------------------------- > Convert auth to Keycloak > ------------------------ > > Key: SRAMP-629 > URL: https://issues.jboss.org/browse/SRAMP-629 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.s... ] Stefan Bunciak commented on SRAMP-16: ------------------------------------- [~bouskaj] increased S-RAMP version to 0.7.0.Final. You can give it another test ride ;-) If you consider it good enough to create a pull request we can do so. > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0.Final > Reporter: Kurt Stam > Assignee: Brett Meyer > Attachments: UIMockup.gliffy, UImockup.gliffy > > > Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful. > One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-631) Fix integration tests to work with KeyCloak

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-631?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-631. ------------------------------ Resolution: Done > Fix integration tests to work with KeyCloak > ------------------------------------------- > > Key: RTGOV-631 > URL: https://issues.jboss.org/browse/RTGOV-631 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Currently integration tests don't work because installation of rtgov into EAP requires an extra manual step of uploading the governance realm. > Started looking into automating this in the integration test scripts, but the problem is that the KeyCloak admin REST API (http://docs.jboss.org/keycloak/docs/1.1.0.Beta2/rest-api/admin/realms/ind...) does not explicit mention what security is used, but is likely to be bearer tokens. Ideally needs to also support basic auth. Need to see if this can be added to kc beta3. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

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 December 2014