January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGTOOL-37) Add support for specifying logger FQCN

by David Lloyd (Created) (JIRA)

Add support for specifying logger FQCN -------------------------------------- Key: LOGTOOL-37 URL: https://issues.jboss.org/browse/LOGTOOL-37 Project: Log Tool Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.CR4 It should be possible to specify in @LogMessage the value to pass as the loggerFqcn, to replace the default (which would be the implementation method's class). In addition, it should be possible to specify an interface parameter to be a @LoggerFQCN, which would set the logger FQCN from that parameter value, overriding the above and the default. -- 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

14 years, 3 months

4
3
0 / 0

[JBoss JIRA] (LOGTOOL-33) Validation of message types fails for out-of-order types

by Sanne Grinovero (Created) (JIRA)

Validation of message types fails for out-of-order types -------------------------------------------------------- Key: LOGTOOL-33 URL: https://issues.jboss.org/browse/LOGTOOL-33 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR2 Reporter: Sanne Grinovero Assignee: David Lloyd >From Infinispan: {code}@LogMessage(level = WARN) @Message(value = "Error committing cache view %2$d for cache %1$s", id = 169) void cacheViewCommitFailure(@Cause Exception e, String cacheName, int committedViewId); {code} {code} Log.java:797: Invalid format for 'Error committing cache view %2$d for cache %1$s' with parameters '[33, JBoss]'. java.util.Formatter Error: d != java.lang.String {code} I think the log message is correct, and the validator should not prevent this from being used. I've a test case ready in a pull request I'm sending now. -- 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

14 years, 3 months

6
5
0 / 0

[JBoss JIRA] (LOGTOOL-34) FQCN methods are not completely correct

by David Lloyd (Created) (JIRA)

FQCN methods are not completely correct --------------------------------------- Key: LOGTOOL-34 URL: https://issues.jboss.org/browse/LOGTOOL-34 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd The generated code looks like this: {code} -- 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

14 years, 3 months

5
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1617) Create a MC bean handle in the likes of java.ejb.Handle

by Carlo de Wolf (JIRA)

Create a MC bean handle in the likes of java.ejb.Handle ------------------------------------------------------- Key: EJBTHREE-1617 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1617 Project: EJB 3.0 Issue Type: Feature Request Components: common Reporter: Carlo de Wolf Assignee: Ales Justin Priority: Critical Fix For: 1.0.0-CR1 -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-153) EJB timer clustering and failover support

by Galder Zamarreno (JIRA)

EJB timer clustering and failover support ----------------------------------------- Key: JBCLUSTER-153 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-153 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Brian Stansberry Support for clustered EJB timer service providing failover -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
7
0 / 0

[JBoss JIRA] Created: (AS7-1738) CLI usability: unclear that the CLI is managing a domain not a host

by Radoslav Husar (JIRA)

CLI usability: unclear that the CLI is managing a domain not a host ------------------------------------------------------------------- Key: AS7-1738 URL: https://issues.jboss.org/browse/AS7-1738 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Alexey Loubyansky Looks to me that the CLI is behaving differently if you are running in a domain mode or in a stadnalone mode managing just a host. However it is not really clear from the CLI help messages. In the following log * the console does not say its running in the domain mode * claims that the --profile argument is optional even though its indeed required * does not say that it is not the master domain controller and refuses all changes anyway {code} [domain@rhusar:9999 /] add-jms-queue --help Synopsis: add-jms-queue [--profile=profile_name] --name=queue_name [--entries=entry(,entry)*] [--selector=selector_name] [--durable=(true|false)] Description: creates a JMS queue Arguments: profile - is allowed and required only in the domain mode, specifies the profile in which the JMS resource should be created. name - the name of the queue. entries - an optional comma-separated list of JNDI names the queue should be bound under. If not present, the name will be used as the JNDI name. selector - optional selector. durable - optional, specifies whether the queue should be durable or not (the default is true). [domain@rhusar:9999 /] add-jms-queue --profile=ha --name=rQ Operation add for address [ ("profile" => "ha"), ("subsystem" => "messaging"), ("jms-queue" => "rQ") ] can only handled by the master Domain Controller; this host is not the master Domain Controller [domain@rhusar:9999 /] add-jms-queue --name=rQ --profile argument value is missing. [domain@rhusar:9999 /] quit Closed connection to rhusar:9999 {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
8
0 / 0

[JBoss JIRA] (AS7-2245) Help text needed for topics

by Kevin Barfield (Created) (JIRA)

Help text needed for topics --------------------------- Key: AS7-2245 URL: https://issues.jboss.org/browse/AS7-2245 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Kevin Barfield Assignee: Heiko Braun There needs to be help text for each topic in the console - this help text should explain what the topic is, why it is important to the user, and maybe a link to the relevant docs section. This needs to be understandable by average people For example: Datasource Configurations Datasources are used to connect JBoss EAP to databases. This page allows admins to view existing datasources Admins can also create, modify, and delete datasources. Please see the datasource section of the documentation for more details about datasources <link>. -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-2329) Web Console: Breadcrumbs in the console to give people context of where they are in UI

by Jim Tyrrell (Created) (JIRA)

Web Console: Breadcrumbs in the console to give people context of where they are in UI -------------------------------------------------------------------------------------- Key: AS7-2329 URL: https://issues.jboss.org/browse/AS7-2329 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell It would be nice to see context of where you are in the UI. -- 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

14 years, 3 months

4
4
0 / 0

[JBoss JIRA] (AS7-2370) Web Console: Datasources do not have the "Edit" Button

by Jim Tyrrell (Created) (JIRA)

Web Console: Datasources do not have the "Edit" Button ------------------------------------------------------ Key: AS7-2370 URL: https://issues.jboss.org/browse/AS7-2370 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Attachments: Screen shot 2011-10-26 at 2.36.39 PM.png The Datasources tab in the console, does not continue the practice of an edit button for making changes to the configuration. See the screen shot for a lack of a screen shot. -- 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

14 years, 3 months

6
7
0 / 0

[JBoss JIRA] (AS7-2645) Test Connection when creating a Data Source, see screen shot

by Jim Tyrrell (Created) (JIRA)

Test Connection when creating a Data Source, see screen shot ------------------------------------------------------------ Key: AS7-2645 URL: https://issues.jboss.org/browse/AS7-2645 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Attachments: Screenshot-3.png When I am creating a data source, and put in the URL, I should have the ability to check make sure the data source URL is valid. Waiting until I have to save it off to test it is a pain, if I fat finger the URL I have about 10 more things to do, to correct it. -- 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

14 years, 3 months

3
2
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 January 2012