December 2012 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-126) client url should not need to include 's-ramp'

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-126?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-126. --------------------------------- Resolution: Done It's now optional. You *can* include the /s-ramp in the endpoint url, but you don't have to. Either will work. > client url should not need to include 's-ramp' > ---------------------------------------------- > > Key: SRAMP-126 > URL: https://issues.jboss.org/browse/SRAMP-126 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Client > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > Before we create demos, we should fix the client url. The spec requires it to start with 's-ramp' as in http://<host>:<port>/<domain>/s-ramp. So when connecting it would make sense you'd only need to specify 'http://<host>:<port>/<domain>', without the 's-ramp' part. This so it can be used to connect to the 'brms' services w/o having to parse out the baseUrl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-126) client url should not need to include 's-ramp'

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-126?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-126. ------------------------------- Note: I also updated all of the demos. Although I left the unit tests alone. > client url should not need to include 's-ramp' > ---------------------------------------------- > > Key: SRAMP-126 > URL: https://issues.jboss.org/browse/SRAMP-126 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Client > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > Before we create demos, we should fix the client url. The spec requires it to start with 's-ramp' as in http://<host>:<port>/<domain>/s-ramp. So when connecting it would make sense you'd only need to specify 'http://<host>:<port>/<domain>', without the 's-ramp' part. This so it can be used to connect to the 'brms' services w/o having to parse out the baseUrl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-126) client url should not need to include 's-ramp'

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-126?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-126: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp-distro/pull/2, https://github.com/Governance/s-ramp/pull/131 > client url should not need to include 's-ramp' > ---------------------------------------------- > > Key: SRAMP-126 > URL: https://issues.jboss.org/browse/SRAMP-126 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Client > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > Before we create demos, we should fix the client url. The spec requires it to start with 's-ramp' as in http://<host>:<port>/<domain>/s-ramp. So when connecting it would make sense you'd only need to specify 'http://<host>:<port>/<domain>', without the 's-ramp' part. This so it can be used to connect to the 'brms' services w/o having to parse out the baseUrl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-132) Increase the memory footprint of JBoss in s-ramp distro

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-132: ----------------------------------- Summary: Increase the memory footprint of JBoss in s-ramp distro Key: SRAMP-132 URL: https://issues.jboss.org/browse/SRAMP-132 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Kurt Stam Fix For: Milestone 3 (Workflow and Relationships) We are currently delegating to the jbpm installer ant script for starting up JBoss. They set the max memory to 512m. We probably need that bumped up to 1024m. We either have to modify their Ant script, or else stop calling them and fire up jboss ourselves. Note - they simply call standalone.sh or standalone.bat, depending on the host system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-131) Review + Test s-ramp distribution

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-131: ----------------------------------- Summary: Review + Test s-ramp distribution Key: SRAMP-131 URL: https://issues.jboss.org/browse/SRAMP-131 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: Milestone 3 (Workflow and Relationships) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-77) Create a distribution with both the S-RAMP server and console

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-77?page=com.atlassian.jira.plugin.s... ] Eric Wittmann updated SRAMP-77: ------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/113, https://github.com/Governance/s-ramp/pull/114, https://github.com/Governance/s-ramp/pull/130, https://github.com/Governance/s-ramp/pull/129, https://github.com/Governance/s-ramp/pull/128 (was: https://github.com/Governance/s-ramp/pull/113, https://github.com/Governance/s-ramp/pull/114) > Create a distribution with both the S-RAMP server and console > ------------------------------------------------------------- > > Key: SRAMP-77 > URL: https://issues.jboss.org/browse/SRAMP-77 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: Milestone 2 (Properties) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > This distribution should include the S-RAMP Server, the client, the console, quickstarts and documentation. As well as a script or instructions to install it to JBossAS-7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-77) Create a distribution with both the S-RAMP server and console

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-77?page=com.atlassian.jira.plugin.s... ] Eric Wittmann closed SRAMP-77. ------------------------------ > Create a distribution with both the S-RAMP server and console > ------------------------------------------------------------- > > Key: SRAMP-77 > URL: https://issues.jboss.org/browse/SRAMP-77 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: Milestone 2 (Properties) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > This distribution should include the S-RAMP Server, the client, the console, quickstarts and documentation. As well as a script or instructions to install it to JBossAS-7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-77) Create a distribution with both the S-RAMP server and console

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-77?page=com.atlassian.jira.plugin.s... ] Eric Wittmann resolved SRAMP-77. -------------------------------- Resolution: Done The s-ramp distro is functioning well now. > Create a distribution with both the S-RAMP server and console > ------------------------------------------------------------- > > Key: SRAMP-77 > URL: https://issues.jboss.org/browse/SRAMP-77 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: Milestone 2 (Properties) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > This distribution should include the S-RAMP Server, the client, the console, quickstarts and documentation. As well as a script or instructions to install it to JBossAS-7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-77) Create a distribution with both the S-RAMP server and console

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-77?page=com.atlassian.jira.plugin.s... ] Work on SRAMP-77 stopped by Eric Wittmann. > Create a distribution with both the S-RAMP server and console > ------------------------------------------------------------- > > Key: SRAMP-77 > URL: https://issues.jboss.org/browse/SRAMP-77 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: Milestone 2 (Properties) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > This distribution should include the S-RAMP Server, the client, the console, quickstarts and documentation. As well as a script or instructions to install it to JBossAS-7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-126) client url should not need to include 's-ramp'

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-126?page=com.atlassian.jira.plugin.... ] Work on SRAMP-126 started by Eric Wittmann. > client url should not need to include 's-ramp' > ---------------------------------------------- > > Key: SRAMP-126 > URL: https://issues.jboss.org/browse/SRAMP-126 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Client > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: Milestone 3 (Workflow and Relationships) > > > Before we create demos, we should fix the client url. The spec requires it to start with 's-ramp' as in http://<host>:<port>/<domain>/s-ramp. So when connecting it would make sense you'd only need to specify 'http://<host>:<port>/<domain>', without the 's-ramp' part. This so it can be used to connect to the 'brms' services w/o having to parse out the baseUrl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues December 2012