October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2183) don't require an id property in generic type commands

by Alexey Loubyansky (Created) (JIRA)

don't require an id property in generic type commands ----------------------------------------------------- Key: AS7-2183 URL: https://issues.jboss.org/browse/AS7-2183 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Beta1 Currently, generic type commands rely on an existing property in the resource which can be used as an instance identifier. Which works for data-source, for example, with its jndi-name. But for, e.g., jms connection factories there is not such property. They are identified by their node name. So, the generic commands should take this into account and support both cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-2182) add generic jms commands

by Alexey Loubyansky (Created) (JIRA)

add generic jms commands ------------------------ Key: AS7-2182 URL: https://issues.jboss.org/browse/AS7-2182 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Beta1 Existing commands like add-jms-queue, remove-jms-queue and others should be deprecated. Instead, new generic commands "a la" data-source should be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9293) Display default interface for a socket-binding-group

by Brian Stansberry (JIRA)

Display default interface for a socket-binding-group ---------------------------------------------------- Key: JBAS-9293 URL: https://issues.jboss.org/browse/JBAS-9293 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web Console Reporter: Brian Stansberry Assignee: Heiko Braun A socket binding group has a default interface attribute that becomes the interface value for any socket binding that doesn't declare one. The Beta7-SNAPSHOT UI isn't showing this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8978) Complete async EJB invocation

by David Lloyd (JIRA)

Complete async EJB invocation ----------------------------- Key: JBAS-8978 URL: https://issues.jboss.org/browse/JBAS-8978 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta2 Integrate the interceptor; test with cancellation; handle @Asynchronous annotation as well as any descriptor stuff -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
10
0 / 0

[JBoss JIRA] Created: (JBRULES-3169) Fix unit tests for drools-persistence-jpa on supported databases

by Marco Rietveld (JIRA)

Fix unit tests for drools-persistence-jpa on supported databases ---------------------------------------------------------------- Key: JBRULES-3169 URL: https://issues.jboss.org/browse/JBRULES-3169 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Marco Rietveld Assignee: Marco Rietveld Priority: Minor See https://hudson.qa.jboss.com/hudson/view/Drools%20jBPM/job/drools-persiste... Drools should support the following databases: - oracle 11g - mssql 2008 R2 - db2 9.7 - mysql 5.1 - mysql 5.0 - postgresql 8.2.x - postgresql 8.3.x - postgresql 8.4.x It's not sure yet of Drools will support the following db's: - sybase 1.5.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-1267) Can't set "append" attribute on file handlers

by Stan Silvert (JIRA)

Can't set "append" attribute on file handlers --------------------------------------------- Key: AS7-1267 URL: https://issues.jboss.org/browse/AS7-1267 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: David Lloyd I can't tell what is really happening here. It seems to parse the "append" attribute OK, but it doesn't show up in the CLI. I've also set it programmatically in the console code, but I never get a value back for it. <periodic-rotating-file-handler name="FILE"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> <append value="true"/> </periodic-rotating-file-handler> [standalone@localhost:9999 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-resource { "outcome" => "success", "result" => { "autoflush" => true, "encoding" => undefined, "file" => { "path" => "server.log", "relative-to" => "jboss.server.log.dir" }, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "level" => "INFO", "suffix" => ".yyyy-MM-dd" } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-885) Not all operations in logging subsystem have an operation-name attribute and reply-, request-properties

by Heiko Rupp (JIRA)

Not all operations in logging subsystem have an operation-name attribute and reply-,request-properties ------------------------------------------------------------------------------------------------------ Key: AS7-885 URL: https://issues.jboss.org/browse/AS7-885 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Rupp [standalone@localhost:9999 console-handler=CONSOLE] :read-resource-description ... "remove" => {"description" => "Remove an existing logging handler."}, "disable" => {"description" => "Disable a logging handler."}, "enable" => {"description" => "Enable a logging handler."}, While the name can be deduced from the key, it is present in many(all?) other subsystem operations and should be available here as well. The operations listed also have no request-properties and reply-properties sections -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1983) Logger handler level should be required

by Tristan Tarrant (JIRA)

Logger handler level should be required --------------------------------------- Key: AS7-1983 URL: https://issues.jboss.org/browse/AS7-1983 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Alpha1 Reporter: Tristan Tarrant Assignee: James Perkins Priority: Minor I believe there is a copy/paste mistake in LoggingSubsystemProviders.java in the following code: private static void addCommonLoggerRequestProperties(final ModelNode modelNode, final ResourceBundle bundle) { modelNode.get(REQUEST_PROPERTIES, LEVEL, TYPE).set(ModelType.STRING); modelNode.get(REQUEST_PROPERTIES, LEVEL, DESCRIPTION).set(bundle.getString("handler.level")); modelNode.get(REQUEST_PROPERTIES, LEVEL, REQUIRED).set(true); modelNode.get(REQUEST_PROPERTIES, FILTER, TYPE).set(ModelType.STRING); modelNode.get(REQUEST_PROPERTIES, FILTER, DESCRIPTION).set(bundle.getString("handler.filter")); modelNode.get(REQUEST_PROPERTIES, LEVEL, REQUIRED).set(false); modelNode.get(REQUEST_PROPERTIES, HANDLERS, TYPE).set(ModelType.LIST); modelNode.get(REQUEST_PROPERTIES, HANDLERS, VALUE_TYPE).set(ModelType.STRING); modelNode.get(REQUEST_PROPERTIES, HANDLERS, DESCRIPTION).set(bundle.getString("logger.handlers")); modelNode.get(REQUEST_PROPERTIES, HANDLERS, REQUIRED).set(false); } the LEVEL property's REQUIRED flag is reset to false, instead of setting the FILTER's flag. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1792) Fix the Logging description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix the Logging description providers for the improved validation in jboss-as-subsystem-test -------------------------------------------------------------------------------------------- Key: AS7-1792 URL: https://issues.jboss.org/browse/AS7-1792 Project: Application Server 7 Issue Type: Feature Request Components: Logging Affects Versions: 7.1.0.Alpha1 Reporter: Kabir Khan Assignee: James Perkins I added a test called LoggingSubsystemTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days. To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() and isValidateOperations() as follows: {code} @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } @Override protected boolean isValidateOperations() { //TODO fix providers https://issues.jboss.org/browse/AS7-1789 return false; } {code} Returning null basically turns off validation of the providers, and the isValidateOperations() override turns off validation of the contents of the actual operations. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples. The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes The above is standard text as I'm going through and creating tests. The test has been @Ignored due to a further failure once validation passes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-9443) BMT Stateful EJB method throwing an Application Exception causes the bean to be destroyed

by Alejandro Giraldo (JIRA)

BMT Stateful EJB method throwing an Application Exception causes the bean to be destroyed ----------------------------------------------------------------------------------------- Key: JBAS-9443 URL: https://issues.jboss.org/browse/JBAS-9443 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.1.0 Environment: Windows XP, JDK 1.6 Reporter: Alejandro Giraldo Assignee: Carlo de Wolf If a BMT Stateful EJB method throws an application exception, the exception gets wrapped in an EJBException whichs causes the bean to be destroyed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011