jopr-issues December 2010

jopr-issues@lists.jboss.org

1 participants
4 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

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

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

4
15
0 / 0

[JBoss JIRA] Commented: (JOPR-362) Validation Error - false alarm on fields marked as unset

by Paul Nittel (JIRA)

[ https://issues.jboss.org/browse/JOPR-362?page=com.atlassian.jira.plugin.s... ] Paul Nittel commented on JOPR-362: ---------------------------------- For the default Oracle XA datasource template, it worked with IE 7.05730, but the generic default datasource template has the false alarm issue. FF 3.5.15 (old, I know) is really hampered by this. Yes, it can be worked around, but fixing it would be more andiamo-like. :-) > Validation Error - false alarm on fields marked as unset > -------------------------------------------------------- > > Key: JOPR-362 > URL: https://issues.jboss.org/browse/JOPR-362 > Project: Jopr > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Ondrej Zizka > Fix For: 2.3 > > Attachments: EmbJopr-validation-error.png > > > Steps to reproduce: > 1) JMS Destinations - Queues - Add a new resource > 2) default, Continue... > 3) Either don't enter anything, or just enter one of the required fields, but not both > 4) Click Add New button at the bottom - validation fails > 5) Either don't enter anything, or fill name and JNDI name, filling in both is ok too. Click Save or Add New > 6) Validation fails on fields that are unset (see the image attached) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 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 December 2010