May 2011 - jboss-jira - Jboss List Archives

[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, 9 months

3
3
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

14 years, 9 months

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

14 years, 9 months

4
12
0 / 0

[JBoss JIRA] Created: (JBLOGGING-52) Use of system property for proxy generation setting is too inflexible

by Dan Allen (JIRA)

Use of system property for proxy generation setting is too inflexible --------------------------------------------------------------------- Key: JBLOGGING-52 URL: https://issues.jboss.org/browse/JBLOGGING-52 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-spi Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd Fix For: 3.0.0.Beta5-jboss-logging JBoss Logging uses a system property to configure whether or not proxies are generated for type-safe loggers. This approach is very inflexible. The main issue is that the value of this system property is being cached too aggressively. In CDI extensions, we are forced to use a static code block to set the property so it is assigned early enough that JBoss Logging caches the correct value. However, with multiple extensions loading in a non-deterministic order, we end up having to put this static block in multiple places. [1] We need a better way to apply this setting. Perhaps a static method on a configuration API to assign the value before any logging takes place. [1] https://github.com/seam/solder/blob/master/impl/src/main/java/org/jboss/s... https://github.com/seam/servlet/blob/master/impl/src/main/java/org/jboss/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
12
0 / 0

[JBoss JIRA] Created: (JBAS-9316) Indentation of multiline text content in standalone.xml keeps increasing on rewrites

by David Bosschaert (JIRA)

Indentation of multiline text content in standalone.xml keeps increasing on rewrites ------------------------------------------------------------------------------------ Key: JBAS-9316 URL: https://issues.jboss.org/browse/JBAS-9316 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: XML Services/Frameworks Affects Versions: 7.0.0.Beta3 Reporter: David Bosschaert Assignee: Jason Greene Priority: Minor The standalone.xml file contains some XML tags that contain multi-line XML text, e.g.: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} The problem is that every automatic rewrite of the standalone.xml (e.g. when you deploy a new thing) the indentation increases from the 2nd line of the text, so after the first rewrite it looks like this: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} after a few deploys it ends up looking like this: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} Pretty ugly :( Would be nice if the indentation could be left untouched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

6
5
0 / 0

[JBoss JIRA] Created: (JBAS-9327) Ensure "add" operation handlers are storing default values

by Brian Stansberry (JIRA)

Ensure "add" operation handlers are storing default values ---------------------------------------------------------- Key: JBAS-9327 URL: https://issues.jboss.org/browse/JBAS-9327 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 In discussion on the dev list we decided to store default values in the model even if not present in XML or in "add" operation params coming from CLI/console. This task is to review the handlers for compliance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-794) Booting slave host controller only makes a single attempt to contact master

by Brian Stansberry (JIRA)

Booting slave host controller only makes a single attempt to contact master --------------------------------------------------------------------------- Key: AS7-794 URL: https://issues.jboss.org/browse/AS7-794 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 RemoteDomainConnectionService tries once to connect; if it fails it gives up immediately and the node switches into slave mode. This needs to be more robust, particularly to handle cases where the master and the slave are starting concurrently (i.e. what should ideally be happening in integration tests). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-9317) Detect crashed DC slave in protocol to avoid errors when restarting crashed slave

by Kabir Khan (JIRA)

Detect crashed DC slave in protocol to avoid errors when restarting crashed slave --------------------------------------------------------------------------------- Key: JBAS-9317 URL: https://issues.jboss.org/browse/JBAS-9317 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.0.0.Beta4 This could be possible with what we have but deferring until we have JBAS-9101 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-740) WS Endpoint doesn't appear in domain mode

by Heiko Braun (JIRA)

WS Endpoint doesn't appear in domain mode ----------------------------------------- Key: AS7-740 URL: https://issues.jboss.org/browse/AS7-740 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Jim Ma I've deployed a sample, can reach it via http, but the list-endpoint op doesn't show it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-9087) Expose the domain management API over JMX

by Brian Stansberry (JIRA)

Expose the domain management API over JMX ----------------------------------------- Key: JBAS-9087 URL: https://issues.jboss.org/browse/JBAS-9087 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.Beta4 Create a JMX domain for the AS 7 management layer; expose management resources as mbeans. Two options: 1) An mbean per resource. 2) Create an adapter layer. Requirement: do not add significant boot time overhead. Populating the mbean server in the background is permissible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
6
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 May 2011