June 2014 - overlord-issues - Jboss List Archives

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

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-437. --------------------------------- Resolution: Done > 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 > > > 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.6#6264)

10 years, 3 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 Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-437: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/79 > 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 > > > 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.6#6264)

10 years, 3 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 Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-437: ------------------------------------- Adding the following markup to web.xml fixes this issue: {code} <context-param> <param-name>org.eclipse.jetty.servlet.SessionIdPathParameterName</param-name> <param-value>none</param-value> </context-param> {code} > 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 > > > 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.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-493) Display conversation and endpoint context information on situation details page

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-493?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-493. ------------------------------ Resolution: Done > Display conversation and endpoint context information on situation details page > ------------------------------------------------------------------------------- > > Key: RTGOV-493 > URL: https://issues.jboss.org/browse/RTGOV-493 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > Currently no context information is displayed for a selected situation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-493) Display conversation and endpoint context information on situation details page

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-493?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-493: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/116 > Display conversation and endpoint context information on situation details page > ------------------------------------------------------------------------------- > > Key: RTGOV-493 > URL: https://issues.jboss.org/browse/RTGOV-493 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > Currently no context information is displayed for a selected situation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-493) Display conversation and endpoint context information on situation details page

by Gary Brown (JIRA)

Gary Brown created RTGOV-493: -------------------------------- Summary: Display conversation and endpoint context information on situation details page Key: RTGOV-493 URL: https://issues.jboss.org/browse/RTGOV-493 Project: RTGov (Run Time Governance) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Currently no context information is displayed for a selected situation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-492) Failed to retrieve situation when selecting situation for non-switchyard promoted service

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-492?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-492. ------------------------------ Resolution: Done > Failed to retrieve situation when selecting situation for non-switchyard promoted service > ----------------------------------------------------------------------------------------- > > Key: RTGOV-492 > URL: https://issues.jboss.org/browse/RTGOV-492 > 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 selecting a situation for an unpromoted switchyard service, it results in a "Unable to retrieve situation" error in the UI. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-492) Failed to retrieve situation when selecting situation for non-switchyard promoted service

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-492?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-492: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/115 > Failed to retrieve situation when selecting situation for non-switchyard promoted service > ----------------------------------------------------------------------------------------- > > Key: RTGOV-492 > URL: https://issues.jboss.org/browse/RTGOV-492 > 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 selecting a situation for an unpromoted switchyard service, it results in a "Unable to retrieve situation" error in the UI. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-431: --------------------------------------- Comment: was deleted (was: I am not sure about this Gary. Normally the test should be in the src/test folder of the project that they are related. In my opinion the ui tests should be in the s-ramp-ui, and the integration tests should be (talking about s-ramp) in the s-ramp-server. Then if we want specific integration tests for every container supported, we could just place the specific tests in every s-ramp-server-container project. Why I am saying this? Because I just created a project s-ramp/s-ramp-test/s-ramp-test-ui and I realized would not be any code in the src/main/ folder. ) > Arquillian-based integration tests > ---------------------------------- > > Key: SRAMP-431 > URL: https://issues.jboss.org/browse/SRAMP-431 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Create a new s-ramp-test module to contain all integration tests. Thoughts: > - 1 central abstract class (IntegrationTest) that contains all the functional tests and assertions (or if that gets too large, split it up into delegates) > - 1 Arquillian test per supported container, extending the above. Mainly in charge of the @RunWith and @Deployments. Ex: EAPIntegrationTest extends IntegrationTest > - None of them should run by default. Pull them all into a specific Maven profile, then setup a new CI job specifically for it. > - 1 central ant script, executed by the POM, should be in charge of downloading the Jetty and and Tomcat distros, then unpacking them. Arquillian would then use them in a "managed mode." > - The ant script will eventually be in charge of downloading EAP as well, but not until we have CI hardware within the RH network. Until then, we'll need to do something similar to RTGov's current tests: require the distro be manually downloaded and unpacked, then set $JBOSS_HOME > - Fuse should be run in embedded mode. > The work-in-progress: https://github.com/brmeyer/s-ramp/commits/integration-tests -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-431: -------------------------------------------- I am not sure about this Gary. Normally the test should be in the src/test folder of the project that they are related. In my opinion the ui tests should be in the s-ramp-ui, and the integration tests should be (talking about s-ramp) in the s-ramp-server. Then if we want specific integration tests for every container supported, we could just place the specific tests in every s-ramp-server-container project. Why I am saying this? Because I just created a project s-ramp/s-ramp-test/s-ramp-test-ui and I realized would not be any code in the src/main/ folder. > Arquillian-based integration tests > ---------------------------------- > > Key: SRAMP-431 > URL: https://issues.jboss.org/browse/SRAMP-431 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Create a new s-ramp-test module to contain all integration tests. Thoughts: > - 1 central abstract class (IntegrationTest) that contains all the functional tests and assertions (or if that gets too large, split it up into delegates) > - 1 Arquillian test per supported container, extending the above. Mainly in charge of the @RunWith and @Deployments. Ex: EAPIntegrationTest extends IntegrationTest > - None of them should run by default. Pull them all into a specific Maven profile, then setup a new CI job specifically for it. > - 1 central ant script, executed by the POM, should be in charge of downloading the Jetty and and Tomcat distros, then unpacking them. Arquillian would then use them in a "managed mode." > - The ant script will eventually be in charge of downloading EAP as well, but not until we have CI hardware within the RH network. Until then, we'll need to do something similar to RTGov's current tests: require the distro be manually downloaded and unpacked, then set $JBOSS_HOME > - Fuse should be run in embedded mode. > The work-in-progress: https://github.com/brmeyer/s-ramp/commits/integration-tests -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

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