July 2011 - jboss-jira - Jboss List Archives

[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

13 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (LOGTOOL-4) Reduce string constants in generated classes

by David Lloyd (JIRA)

Reduce string constants in generated classes -------------------------------------------- Key: LOGTOOL-4 URL: https://jira.jboss.org/browse/LOGTOOL-4 Project: Log Tool Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Minor The generated classes include pregenerated string constants e.g. "PROJECT-00001" etc. This can be wasteful of space and constant table entries. These prefixes should be programmatically generated at the time of message rendering. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (LOGTOOL-5) Support BasicLogger methods on logger interfaces

by David Lloyd (JIRA)

Support BasicLogger methods on logger interfaces ------------------------------------------------ Key: LOGTOOL-5 URL: https://issues.jboss.org/browse/LOGTOOL-5 Project: Log Tool Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta1 Reporter: David Lloyd Fix For: 1.0.0.Beta2 If a logger interface extends BasicLogger, then those methods should be implemented and delegated to the logger instance. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (LOGTOOL-2) Message logger will not allow String return type

by James Perkins (JIRA)

Message logger will not allow String return type ------------------------------------------------ Key: LOGTOOL-2 URL: https://jira.jboss.org/browse/LOGTOOL-2 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta1 Reporter: James Perkins Assignee: David Lloyd Interfaces annotated with @MessageLogger should allow String return types if and only if the @LogMessage annotation is not present on the method. Also, the @LogMessage annotation should not be inherited on like named methods. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (LOGTOOL-21) Add mechanism to pass parameters to exception constructors

by David Lloyd (JIRA)

Add mechanism to pass parameters to exception constructors ---------------------------------------------------------- Key: LOGTOOL-21 URL: https://issues.jboss.org/browse/LOGTOOL-21 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: James Perkins Fix For: 1.0.0.Beta8 We need a parameter annotation which allows log methods to pass additional parameters to the constructor of exceptions. Something like {{@Param}}. It would exclude that parameter from the list and instead apply those values to non-cause, non-message parameters of the constructor. For the purposes of resolution, assume the message parameter is the left-most String and the cause parameter is the left-most Throwable or subtype thereof. Parameters should be order-matched first, then type-matched to resolve ambiguity, throwing an exception if there is no unambiguous solution. The {{@Param}} annotation should allow an optional class name to be specified which would have to match the exact type of the parameter in question, to enable unambiguous resolution in this case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-1435) Modify cobertura maven plugin definition to use version 2.5

by Rostislav Svoboda (JIRA)

Modify cobertura maven plugin definition to use version 2.5 ----------------------------------------------------------- Key: AS7-1435 URL: https://issues.jboss.org/browse/AS7-1435 Project: Application Server 7 Issue Type: Task Reporter: Rostislav Svoboda Upgrade jboss-parent to use version 2.5 for cobertura maven plugin. Version 2.5 contains functionality for agregated report - http://jira.codehaus.org/browse/MCOBERTURA-65 Don't use version 2.5.1 because there is NPE bug - see http://jira.codehaus.org/browse/MCOBERTURA-151 Workaround: specify cobertura plugin version from command line mvn -Pcode-coverage -Dcobertura.aggregate=true -Dversion.cobertura.plugin=2.5 clean cobertura:clean cobertura:cobertura -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
6
0 / 0

[JBoss JIRA] Created: (AS7-815) Fix or remove ignored tests in WSTestCase

by Thomas Diesler (JIRA)

Fix or remove ignored tests in WSTestCase ----------------------------------------- Key: AS7-815 URL: https://issues.jboss.org/browse/AS7-815 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Alessio Soldano We are in the process of a major test infrastructure update. For this I migrated all smoke tests the the managed container. The arquillian subsystem has been replaced by a on-demand deployment. Your test might be @Ignored because I could not fix it easily or it has already been ignored for some time. Please have a look if you can fix it, otherwise I'd like to know why it should be ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

7
7
0 / 0

[JBoss JIRA] Created: (AS7-1080) XA Datasource w/o xa-properties swllows an exception

by Heiko Braun (JIRA)

XA Datasource w/o xa-properties swllows an exception ---------------------------------------------------- Key: AS7-1080 URL: https://issues.jboss.org/browse/AS7-1080 Project: Application Server 7 Issue Type: Bug Reporter: Heiko Braun Fix For: 7.1.0.Alpha1 ry to add an XA Datasource but don't add any XA properties. You will get the error below on the server. The problem is that the user doesn't see any error message at all. I assume that this is a known class of problem, but I mention here for bookkeeping purposes. 12:45:43,109 WARN [org.jboss.as.controller] (HttpManagementService-threads - 4) Operation ("add") failed - address: ([ ("subsystem" => "datasources"), ("xa-data-source" => "foo") ]): org.jboss.as.controller.OperationFailedException: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in o rg.jboss.jca.common.metadata.ds.XADataSourceImpl [ "Failed to create XaDataSource instance for [{ \"operation\" => \"add\", \"address\" => [ (\"subsystem\" => \"datasources\"), (\"xa-data-source\" => \"foo\") ], \"name\" => \"foo\", \"jndi-name\" => \"bar\", \"enabled\" => true, \"driver-name\" => \"h2\", \"driver-class-name\" => \"org.h2.Driver\", \"driver-major-version\" => 1, \"driver-minor-version\" => 2, \"pool-name\" => \"foo_Pool\", \"user-name\" => \"asdf\", \"password\" => \"asdf\", \"xa-data-source-properties\" => {} }] reason:IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.XADataSourceImpl" ] at org.jboss.as.connector.subsystems.datasources.XaDataSourceAdd.startConfigAndAddDependency(XaDataSourceAdd.java:64) at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceAdd.performRuntime(AbstractDataSourceAdd.java:93) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1310) Manage resource adapters through web console

by Heiko Braun (JIRA)

Manage resource adapters through web console -------------------------------------------- Key: AS7-1310 URL: https://issues.jboss.org/browse/AS7-1310 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1100) ENCRYPT debug log prints "hex" output in ambiguous format

by Dennis Reed (JIRA)

ENCRYPT debug log prints "hex" output in ambiguous format --------------------------------------------------------- Key: JGRP-1100 URL: https://jira.jboss.org/jira/browse/JGRP-1100 Project: JGroups Issue Type: Bug Affects Versions: 2.4.7 Reporter: Dennis Reed Assignee: Dennis Reed ENCRYPT.formatArray doesn't convert a byte array straight to hex. It leaves off any leading 0 in a byte and appends ffffff in front of any negative byte. This prevents the original data from easily being reconstructed from the log for debugging purposes. -- 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, 2 months

4
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011