July 2012 - jboss-jira - Jboss List Archives

[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-52) Remove string concatenation during message construction

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-52: ---------------------------------- Summary: Remove string concatenation during message construction Key: LOGTOOL-52 URL: https://issues.jboss.org/browse/LOGTOOL-52 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Bill Burke Assignee: David Lloyd Fix For: 1.0.3.Final, 1.1.0.Beta1 I have noticed a small deficiency in your otherwise completely excellent software! As it turns out, the source code generation produces superfluous string concatenations. It would be more efficient if the string concatenation were to happen either during processing, or within the right-hand side of the static field assignment expression in the generated classes. Keep up the top-notch work on the definitely not over-engineered project! Excelsior!! -- 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

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

[JBoss JIRA] (LOGTOOL-46) jboss-logging-generator singletons don't play nice with Eclipse APT

by Fred Bricon (JIRA)

Fred Bricon created LOGTOOL-46: ---------------------------------- Summary: jboss-logging-generator singletons don't play nice with Eclipse APT Key: LOGTOOL-46 URL: https://issues.jboss.org/browse/LOGTOOL-46 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR5 Environment: Eclipse 3.7 Reporter: Fred Bricon Assignee: David Lloyd Attachments: jbosslogging-ap-errors.png While testing [m2e-apt|https://github.com/jbosstools/m2e-apt] on [hibernate-search|https://github.com/hibernate/hibernate-search], I got these strange errors : all the log methods are marked as being duplicate. My gut feeling is this is due to [MessageIdValidator being a singleton|https://github.com/jboss-logging/jboss-logging-tools/blob/4b437...] : all AP work in eclipse reuses the same instance between each incremental builds. So validating the same file more than once lead to these errors. -- 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

3
8
0 / 0

[JBoss JIRA] (LOGTOOL-44) Make configurable whether @Override annotation shall be added

by Gunnar Morling (JIRA)

Gunnar Morling created LOGTOOL-44: ------------------------------------- Summary: Make configurable whether @Override annotation shall be added Key: LOGTOOL-44 URL: https://issues.jboss.org/browse/LOGTOOL-44 Project: Log Tool Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Gunnar Morling Assignee: David Lloyd The annotation processor adds the {{(a)java.lang.Override}} annotation to the methods of generated log or message bundle classes. For methods implementing interface methods this is allowed only in Java 6 and above, while in Java 5 {{@Override}} is only allowed for methods overriding methods from superclasses. Therefore compilation of the generated classes fails using Java 5. To address this issue, the annotation should be added conditionally based on the current source level. -- 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
19
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 2012