April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6834) The Resource Adapter Properties become editable clicking in the Resource Adapters.

by William Siqueira (JIRA)

[ https://issues.jboss.org/browse/AS7-6834?page=com.atlassian.jira.plugin.s... ] William Siqueira updated AS7-6834: ---------------------------------- > The Resource Adapter Properties become editable clicking in the Resource Adapters. > ---------------------------------------------------------------------------------- > > Key: AS7-6834 > URL: https://issues.jboss.org/browse/AS7-6834 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Domain Management > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Leticia Konno > Assignee: Heiko Braun > Priority: Minor > Attachments: gui1.zip > > > The Resource Adapter Properties becomes editable clicking in the Resource Adapters. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6834) The Resource Adapter Properties become editable clicking in the Resource Adapters.

by Leticia Konno (JIRA)

[ https://issues.jboss.org/browse/AS7-6834?page=com.atlassian.jira.plugin.s... ] Leticia Konno updated AS7-6834: ------------------------------- Steps to Reproduce: 1. navigate to a connection definition of a RA (resource adapter) 2. navigate to the "properties" tab and click at any of them (gui1.png) 3. click at other connection definition 4. click on the previous connection definition 5. this time the property field is in a text field to edit (gui2.png), the user can type anything and click at anywhere in the screen, the field retain the changes (gui3.png). It is possible to do it with all the fields (gui4.png). was: 1. navigate to a connection definition of a RA (resource adapter) java:/mq/MqChannelOfpub 2. navigate to the "properties" tab and click at any of them (gui1.png) 3. click at other connection definition 4. click on the previous connection definition 5. this time the property field is in a text field to edit (gui2.png), the user can type anything and click at anywhere in the screen, the field retain the changes (gui3.png). It is possible to do it with all the fields (gui4.png). > The Resource Adapter Properties become editable clicking in the Resource Adapters. > ---------------------------------------------------------------------------------- > > Key: AS7-6834 > URL: https://issues.jboss.org/browse/AS7-6834 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Domain Management > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Leticia Konno > Assignee: Heiko Braun > Priority: Minor > Attachments: gui1.zip > > > The Resource Adapter Properties becomes editable clicking in the Resource Adapters. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6834) The Resource Adapter Properties become editable clicking in the Resource Adapters.

by Leticia Konno (JIRA)

[ https://issues.jboss.org/browse/AS7-6834?page=com.atlassian.jira.plugin.s... ] Leticia Konno updated AS7-6834: ------------------------------- Summary: The Resource Adapter Properties become editable clicking in the Resource Adapters. (was: The Resource Adapter Properties becomes editable clicking in the Resource Adapters.) > The Resource Adapter Properties become editable clicking in the Resource Adapters. > ---------------------------------------------------------------------------------- > > Key: AS7-6834 > URL: https://issues.jboss.org/browse/AS7-6834 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Domain Management > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Leticia Konno > Assignee: Heiko Braun > Priority: Minor > Attachments: gui1.zip > > > The Resource Adapter Properties becomes editable clicking in the Resource Adapters. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6834) The Resource Adapter Properties becomes editable clicking in the Resource Adapters.

by Leticia Konno (JIRA)

Leticia Konno created AS7-6834: ---------------------------------- Summary: The Resource Adapter Properties becomes editable clicking in the Resource Adapters. Key: AS7-6834 URL: https://issues.jboss.org/browse/AS7-6834 Project: Application Server 7 Issue Type: Bug Components: Console, Domain Management Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.3.Final (EAP) Reporter: Leticia Konno Assignee: Heiko Braun Priority: Minor Attachments: gui1.zip The Resource Adapter Properties becomes editable clicking in the Resource Adapters. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6834) The Resource Adapter Properties become editable clicking in the Resource Adapters.

by Leticia Konno (JIRA)

[ https://issues.jboss.org/browse/AS7-6834?page=com.atlassian.jira.plugin.s... ] Leticia Konno updated AS7-6834: ------------------------------- Attachment: gui1.zip > The Resource Adapter Properties become editable clicking in the Resource Adapters. > ---------------------------------------------------------------------------------- > > Key: AS7-6834 > URL: https://issues.jboss.org/browse/AS7-6834 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Domain Management > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Leticia Konno > Assignee: Heiko Braun > Priority: Minor > Attachments: gui1.zip > > > The Resource Adapter Properties becomes editable clicking in the Resource Adapters. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6664: ---------------------------------------------- pkremens(a)redhat.com made a comment on [bug 915317|https://bugzilla.redhat.com/show_bug.cgi?id=915317] Verified on EAP 6.1.0 ER4 > Unable to turn on/off logging handlers using enable()/disable() in CLI > ---------------------------------------------------------------------- > > Key: AS7-6664 > URL: https://issues.jboss.org/browse/AS7-6664 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Logging > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Peter Kremens reports: > I am unable to use enable/disable operation in logging handlers. > > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Calling disable() won't affect enabled attribute > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Must use write-attribute instead > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => false, > ... > } > } > {code} -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6664: ---------------------------------------------- pkremens(a)redhat.com changed the Status of [bug 915317|https://bugzilla.redhat.com/show_bug.cgi?id=915317] from ON_QA to VERIFIED > Unable to turn on/off logging handlers using enable()/disable() in CLI > ---------------------------------------------------------------------- > > Key: AS7-6664 > URL: https://issues.jboss.org/browse/AS7-6664 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Logging > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Peter Kremens reports: > I am unable to use enable/disable operation in logging handlers. > > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Calling disable() won't affect enabled attribute > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Must use write-attribute instead > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => false, > ... > } > } > {code} -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5855) CLONE - vault script generates identical shared keys when adding multiple passwords in one session

by Geoffrey Bays (JIRA)

[ https://issues.jboss.org/browse/AS7-5855?page=com.atlassian.jira.plugin.s... ] Geoffrey Bays commented on AS7-5855: ------------------------------------ I am aware of this bug, and have used two interactive sessions to generate two distinct handles to two passwords in the vault. Anyone know of an example of referencing two passwords from the vault in standalone.xml?? I am unable to get this to work. I know, this is not a help forum, but here is my issue below. Or is there a bug here as well?? I need an example of putting two passwords into the vault and then referencing them in standalone.xml. I have referenced the keystore file and password via the vault in the ssl connector line in standalone.xml, and have put the following reference to the truststore and password in as system properties. If I hardcode the unmasked truststore password all works, but even when using two interactive sessions (so that I get a separate handle for the second password), I cannot put two passwords into the vault and get the truststore reference to work. I get IOException: keystore was tampered with of password is incorrect. In standalone.xml: <system-property> <property name="javax.net.ssl.trustStore" value="Path /to/truststore/file" /> <property name="javax.net.ssl.trustStorePassword" value="VAULT::truststore_pass::password::YjdkMDU10TMzTdmy........." /> </system-property> Do I need more lines in the <vault> <vault-option> section to reference the second password? Two vault tags will not parse. Any suggestions or two password example would be most welcome. I have tried referencing the keystore password with the same vault handle since it is the same--does not work. And I have generated vault dat files using a reference to the keystore alone or with a separate reference to the truststore. Neither approach works. Thanks Geoffrey Bays > CLONE - vault script generates identical shared keys when adding multiple passwords in one session > -------------------------------------------------------------------------------------------------- > > Key: AS7-5855 > URL: https://issues.jboss.org/browse/AS7-5855 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts, Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: Tom Fonteyne > > Adding multiple passwords in a single interactive session with vault.sh generates duplicate Shared Keys -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-95) Statefull memory corruption with insertLogical() and 2 nots

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-95: -------------------------------------- Summary: Statefull memory corruption with insertLogical() and 2 nots Key: DROOLS-95 URL: https://issues.jboss.org/browse/DROOLS-95 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Beta1 Reporter: Geoffrey De Smet Assignee: Mario Fusco Priority: Critical Statefull corruption in RETE. Ping ge0ffrey on IRC if you have ample time and a clear head. This bug is nasty :) -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6553) Parent Issue for Java EE 7 Support

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-6553?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-6553: ---------------------------------- Thanks, I had missed that one. > Parent Issue for Java EE 7 Support > ---------------------------------- > > Key: AS7-6553 > URL: https://issues.jboss.org/browse/AS7-6553 > Project: Application Server 7 > Issue Type: Task > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Critical > Fix For: 8.0.0.Alpha1 > > > This is the parent issue for tracking tasks related to completing our Java EE 7 support. Do not close the issue unless Jason has given his blessing. -- 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013