July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-747) Subsystem "web": Boolean model values must not be "undefined"

by Heiko Braun (JIRA)

Subsystem "web": Boolean model values must not be "undefined" ------------------------------------------------------------- Key: AS7-747 URL: https://issues.jboss.org/browse/AS7-747 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
9
0 / 0

[JBoss JIRA] Created: (AS7-1299) Interface resource's criteria attribute should be read-write

by Brian Stansberry (JIRA)

Interface resource's criteria attribute should be read-write ------------------------------------------------------------- Key: AS7-1299 URL: https://issues.jboss.org/browse/AS7-1299 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.1.0.Alpha1 http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003123.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
10
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

14 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

14 years, 8 months

6
10
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

14 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 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

14 years, 8 months

4
4
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 July 2011