jopr-issues September 2010

jopr-issues@lists.jboss.org

1 participants
5 discussions

[JBoss JIRA] Created: (JOPR-73) Add support for changing arguments passed to start/stop operations

by Charles Crouch (JIRA)

Add support for changing arguments passed to start/stop operations ------------------------------------------------------------------ Key: JOPR-73 URL: https://jira.jboss.org/jira/browse/JOPR-73 Project: Jopr Issue Type: Feature Request Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5 Reporter: Charles Crouch Comes out of case: 264527 Right now if you change the start/stop scripts used by a JBAS instance the new scripts have to understand the same arguments which the default jbas ones takes, e.g. for shutdown thats: --server=jnp://localhost:1099 --user=myuser --password=mypassword --shutdown Given we enable people to specify their own scripts for these operations we should enable them to configure the arguments we pass to the scripts, just like we do when executing a JBAS script resource. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JOPR-105) ManagedComponetComponent.invokeOperation() assumes there is only one ManagedOperation with a given name, which may not be true

by Ian Springer (JIRA)

ManagedComponetComponent.invokeOperation() assumes there is only one ManagedOperation with a given name, which may not be true ------------------------------------------------------------------------------------------------------------------------------ Key: JOPR-105 URL: https://jira.jboss.org/jira/browse/JOPR-105 Project: Jopr Issue Type: Bug Components: Plugin - JBoss AS 5 Affects Versions: 2.1 Reporter: Ian Springer Assignee: Ian Springer Fix For: 2.2 The ManagedComponent could have more than one operation with a given name (i.e. overloaded operations), so we need to examine the parameters too to figure out the correct operation to invoke. Here's an email I sent to Scott: Ian Springer wrote: > Scott- > > Quick question. Will ManagedComponent.getOperations() ever return multiple operations with the same name (i.e. overloaded operations)? > > Thanks, > Ian Yes, it should. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JOPR-95) EWS TC5 web.xml is missing a <filter-mapping/> section

by Heiko W. Rupp (JIRA)

EWS TC5 web.xml is missing a <filter-mapping/> section ------------------------------------------------------ Key: JOPR-95 URL: https://jira.jboss.org/jira/browse/JOPR-95 Project: Jopr Issue Type: Bug Components: Plugin - Tomcat Affects Versions: 2.2 Reporter: Heiko W. Rupp Priority: Blocker Fix For: 2.2 EWS tC 5 web.xml has a <filter> section for the Rtfilter, but is missing a <filter-mapping/> section Only enabling the <filter> section and restarting TC results in a unusable server <filter-mapping> <filter-name>RhqRtFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
15
0 / 0

[JBoss JIRA] Closed: (JOPR-419) EAP or SOA-P 5 when started without -c is defined with wrong config, and when started without -b is defined with wrong bind address

by Pavel Kralik (JIRA)

[ https://jira.jboss.org/browse/JOPR-419?page=com.atlassian.jira.plugin.sys... ] Pavel Kralik closed JOPR-419. ----------------------------- Regression tested with SOA-P 5.1.0.ER1 and JON 2.4.0.GA (PostgreSQL 8.3.8), OpenJDK/SunJDK 1.6. > EAP or SOA-P 5 when started without -c is defined with wrong config, and when started without -b is defined with wrong bind address > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JOPR-419 > URL: https://jira.jboss.org/browse/JOPR-419 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 5 > Affects Versions: 2.3 > Environment: JON 2.3.0 GA + SOA plugin pack + SOA-P 5 (EAP5) > Reporter: Jaroslaw Kijanowski > Assignee: Pavel Kralik > Fix For: 2.4 > > > I start SOA-P5/EAP5 without any params (no -c and no -b). This starts the app server with the "default" profile. > Discovered is the production config (which was the default one in 4.x) however in 5.x the default is default again. > Also, the conn props show that it is bound to 0.0.0.0 which is also not true. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JOPR-419) EAP or SOA-P 5 when started without -c is defined with wrong config, and when started without -b is defined with wrong bind address

by Pavel Kralik (JIRA)

[ https://jira.jboss.org/browse/JOPR-419?page=com.atlassian.jira.plugin.sys... ] Pavel Kralik resolved JOPR-419. ------------------------------- Assignee: Pavel Kralik Resolution: Done > EAP or SOA-P 5 when started without -c is defined with wrong config, and when started without -b is defined with wrong bind address > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JOPR-419 > URL: https://jira.jboss.org/browse/JOPR-419 > Project: Jopr > Issue Type: Bug > Components: Plugin - JBoss AS 5 > Affects Versions: 2.3 > Environment: JON 2.3.0 GA + SOA plugin pack + SOA-P 5 (EAP5) > Reporter: Jaroslaw Kijanowski > Assignee: Pavel Kralik > Fix For: 2.4 > > > I start SOA-P5/EAP5 without any params (no -c and no -b). This starts the app server with the "default" profile. > Discovered is the production config (which was the default one in 4.x) however in 5.x the default is default again. > Also, the conn props show that it is bound to 0.0.0.0 which is also not true. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

← Newer
1
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jopr-issues September 2010