April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1263) Publish deployment descriptor schemas and dtd in the dist

by Brian Stansberry (JIRA)

Publish deployment descriptor schemas and dtd in the dist --------------------------------------------------------- Key: AS7-1263 URL: https://issues.jboss.org/browse/AS7-1263 Project: Application Server 7 Issue Type: Task Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.0.1.Final AS 7.0 has the domain/host/standalone config schemas in docs/schema, but not the deployment descriptor schemas and DTDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
14
0 / 0

[JBoss JIRA] (AS7-4057) Create logging profiles for deployments

by James Perkins (JIRA)

James Perkins created AS7-4057: ---------------------------------- Summary: Create logging profiles for deployments Key: AS7-4057 URL: https://issues.jboss.org/browse/AS7-4057 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.Alpha1 Create logging profiles to be assignable to deployments. The precedence would be deployment configuration -> profile configuration -> default configuration. This would allow profiles to be configured with the management interface. Each profile would have it's own LogContext and the context could be secured. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (AS7-2385) Management - readding file handler logger fails

by Dominik Pospisil (Created) (JIRA)

Management - readding file handler logger fails ----------------------------------------------- Key: AS7-2385 URL: https://issues.jboss.org/browse/AS7-2385 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Logging Affects Versions: 7.1.0.Beta1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Removing and adding file handler fails. Perhaps remove operation does not clean up all resources properlly. Steps to reproduce: [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:remove {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) { "outcome" => "failed", "failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.logging.handler-file.test-fh is already registered", "rolled-back" => true } [standalone@localhost:9999 /] -- 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

13 years, 10 months

6
5
0 / 0

[JBoss JIRA] (AS7-2873) EJB not defining an EJB 2 view method should not deploy

by Carlo de Wolf (Created) (JIRA)

EJB not defining an EJB 2 view method should not deploy ------------------------------------------------------- Key: AS7-2873 URL: https://issues.jboss.org/browse/AS7-2873 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Carlo de Wolf Assignee: Stuart Douglas A bean which does not implement the sayHello method of the following EJB 2 remote view: {code:title=HelloRemote.java} public interface HelloRemote extends EJBObject { String sayHello(String name) throws RemoteException; } {code} gets the following exception during invocation: {noformat} Caused by: javax.ejb.EJBException: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit) at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:241) at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:201) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:86) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:56) ... 126 more {noformat} Instead the EJB should not have deployed properly and throw a DeploymentException. -- 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

13 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (LOGTOOL-22) Add additional support for message validation.

by James Perkins (JIRA)

Add additional support for message validation. ---------------------------------------------- Key: LOGTOOL-22 URL: https://issues.jboss.org/browse/LOGTOOL-22 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: David Lloyd Fix For: 1.0.0.Beta8 Add validation to see if the method parameters match the parameters required for the message. For example, an integer should be passed to String.format("%d"). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
9
0 / 0

[JBoss JIRA] (LOGTOOL-40) Generated translations are being generated with the last message generated for all languages

by James Perkins (JIRA)

James Perkins created LOGTOOL-40: ------------------------------------ Summary: Generated translations are being generated with the last message generated for all languages Key: LOGTOOL-40 URL: https://issues.jboss.org/browse/LOGTOOL-40 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Final Reporter: James Perkins Assignee: James Perkins Priority: Blocker -- 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

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (LOGTOOL-39) readResolve methods should return type Object.

by James Perkins (JIRA)

James Perkins created LOGTOOL-39: ------------------------------------ Summary: readResolve methods should return type Object. Key: LOGTOOL-39 URL: https://issues.jboss.org/browse/LOGTOOL-39 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins -- 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

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] (LOGTOOL-42) Message.INHERIT does not property inherit the id on overloaded methods.

by James Perkins (JIRA)

James Perkins created LOGTOOL-42: ------------------------------------ Summary: Message.INHERIT does not property inherit the id on overloaded methods. Key: LOGTOOL-42 URL: https://issues.jboss.org/browse/LOGTOOL-42 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins When overloaded methods are used the the message id is set to be inherited, the message id is not really inherited unless the overloaded methods contain the exact same number of parameters (minus any @Param, @Field or @Cause annotated parameters). -- 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

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (LOGTOOL-41) Add better comments for parameter arguments in the skeleton files.

by James Perkins (JIRA)

James Perkins created LOGTOOL-41: ------------------------------------ Summary: Add better comments for parameter arguments in the skeleton files. Key: LOGTOOL-41 URL: https://issues.jboss.org/browse/LOGTOOL-41 Project: Log Tool Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Add the parameter name and possibly the JavaDoc for the parameter in the skeleton translation files. {code:java} String sayHello(String name) {code} Should generate: {code} # Id: 100 # Level: Logger.Level.INFO # Message: Hello %s[1]. # [1]: name {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

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (LOGTOOL-43) Double-byte characters are not correctly generated in the source

by James Perkins (JIRA)

James Perkins created LOGTOOL-43: ------------------------------------ Summary: Double-byte characters are not correctly generated in the source Key: LOGTOOL-43 URL: https://issues.jboss.org/browse/LOGTOOL-43 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.2.Final When a translation file (a properties file) used double-byte characters, the generated source string is incorrect due to improper loading of the properties file. -- 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

13 years, 10 months

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