May 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-429) Move jetty login-realm config from s-ramp installer to overlord-commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-429. --------------------------------- Resolution: Done > Move jetty login-realm config from s-ramp installer to overlord-commons installer > --------------------------------------------------------------------------------- > > Key: SRAMP-429 > URL: https://issues.jboss.org/browse/SRAMP-429 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Currently we simply replace the jetty.xml in the s-ramp installer for jetty8. Instead we should transform the existing one to add what we want. The s-ramp installer should add the s-ramp datasource. The overlord-commons installer should add the idp realm. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-429) Move jetty login-realm config from s-ramp installer to overlord-commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-429: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/68 > Move jetty login-realm config from s-ramp installer to overlord-commons installer > --------------------------------------------------------------------------------- > > Key: SRAMP-429 > URL: https://issues.jboss.org/browse/SRAMP-429 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Currently we simply replace the jetty.xml in the s-ramp installer for jetty8. Instead we should transform the existing one to add what we want. The s-ramp installer should add the s-ramp datasource. The overlord-commons installer should add the idp realm. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-467) Conflict when multiple elasticsearch clients trying to create same index

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-467?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-467. ------------------------------ Resolution: Done > Conflict when multiple elasticsearch clients trying to create same index > ------------------------------------------------------------------------ > > Key: RTGOV-467 > URL: https://issues.jboss.org/browse/RTGOV-467 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Exceptions reporting that index already created. > Also seen exceptions indicating parent/child relationship not defined for activity unit. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-467) Conflict when multiple elasticsearch clients trying to create same index

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-467?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-467: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/89 > Conflict when multiple elasticsearch clients trying to create same index > ------------------------------------------------------------------------ > > Key: RTGOV-467 > URL: https://issues.jboss.org/browse/RTGOV-467 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Exceptions reporting that index already created. > Also seen exceptions indicating parent/child relationship not defined for activity unit. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-429) Move jetty login-realm config from s-ramp installer to overlord-commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.... ] Work on SRAMP-429 started by Eric Wittmann. > Move jetty login-realm config from s-ramp installer to overlord-commons installer > --------------------------------------------------------------------------------- > > Key: SRAMP-429 > URL: https://issues.jboss.org/browse/SRAMP-429 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Currently we simply replace the jetty.xml in the s-ramp installer for jetty8. Instead we should transform the existing one to add what we want. The s-ramp installer should add the s-ramp datasource. The overlord-commons installer should add the idp realm. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-385) S-RAMP 0.4.0.Final broken in Fuse 6.1

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-385?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-385: ------------------------------ Fix Version/s: (was: 0.5.0.Final) > S-RAMP 0.4.0.Final broken in Fuse 6.1 > ------------------------------------- > > Key: SRAMP-385 > URL: https://issues.jboss.org/browse/SRAMP-385 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Kurt Stam > > I believe the change to making S-RAMP persistent in tomcat has broken fuse 6.1 support. The 0.4.0.Final installer works ok but s-ramp tries to look for a file called "infinispan-configuration-tomcat.xml" and fails. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-385) S-RAMP 0.4.0.Final broken in Fuse 6.1

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-385?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-385. ----------------------------- Resolution: Out of Date Between Eric's fix and our latest Fuse work, calling this one out-of-date. > S-RAMP 0.4.0.Final broken in Fuse 6.1 > ------------------------------------- > > Key: SRAMP-385 > URL: https://issues.jboss.org/browse/SRAMP-385 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Kurt Stam > > I believe the change to making S-RAMP persistent in tomcat has broken fuse 6.1 support. The 0.4.0.Final installer works ok but s-ramp tries to look for a file called "infinispan-configuration-tomcat.xml" and fails. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-429) Move jetty login-realm config from s-ramp installer to overlord-commons installer

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-429: ------------------------------ Fix Version/s: 0.5.0.Alpha1 > Move jetty login-realm config from s-ramp installer to overlord-commons installer > --------------------------------------------------------------------------------- > > Key: SRAMP-429 > URL: https://issues.jboss.org/browse/SRAMP-429 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Currently we simply replace the jetty.xml in the s-ramp installer for jetty8. Instead we should transform the existing one to add what we want. The s-ramp installer should add the s-ramp datasource. The overlord-commons installer should add the idp realm. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-437) Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-437: ------------------------------ Fix Version/s: 0.5.0.Alpha1 > Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1 > ----------------------------------------------------------------------- > > Key: SRAMP-437 > URL: https://issues.jboss.org/browse/SRAMP-437 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > After the first time it works ok. Probably has something to do with the ;jessionid= that is getting dumped onto the end of the URL. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-423) Enable SRAMP to be deployed to fabric as a profile

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-423: ------------------------------ Fix Version/s: 0.5.0.Alpha1 > Enable SRAMP to be deployed to fabric as a profile > -------------------------------------------------- > > Key: SRAMP-423 > URL: https://issues.jboss.org/browse/SRAMP-423 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Enable SRAMP to be deployed to fabric as a profile. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2014