May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-312) Use determineResolvedJndiName in getInvokerBinding of EJB2.x entity and session bean metadata

by jaikiran pai (JIRA)

Use determineResolvedJndiName in getInvokerBinding of EJB2.x entity and session bean metadata --------------------------------------------------------------------------------------------- Key: JBMETA-312 URL: https://jira.jboss.org/browse/JBMETA-312 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jboss-metadata-ejb-2.0.0-alpha-21 Reporter: jaikiran pai Assignee: jaikiran pai The getInvokerBinding in EntityMetaData and SessionMetaData currently don't take into account the binding policy while generating the jndi name. These methods should use the determineResolvedJndiName to utilize the binding policy while resolving the jndi name. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8569) Disable ENC injector creations in EJB container

by jaikiran pai (JIRA)

Disable ENC injector creations in EJB container ------------------------------------------------ Key: JBAS-8569 URL: https://jira.jboss.org/browse/JBAS-8569 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: jaikiran pai Assignee: jaikiran pai -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-8846) JEE 6 application gives errors when deploying having ejb-jar.xml contain module name tag

by Viggo Navarsete (JIRA)

JEE 6 application gives errors when deploying having ejb-jar.xml contain module name tag ---------------------------------------------------------------------------------------- Key: JBAS-8846 URL: https://issues.jboss.org/browse/JBAS-8846 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Viggo Navarsete I've bundled an EAR with maven-ear-plugin (version 2.5-SNAPSHOT, with Java EE 6 features), where I've set the module-name in ejb-jar.xml to tell how the JNDI tree should give names to EJB's in the application. Stacktrace: 09:55:48,689 WARN [org.jboss.profileservice.deployment.hotdeploy.HDScanner] Scan failed: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss-switchboard:appName=mds-ear-1.1.9-SNAPSHOT,module=mds-console-web-1.1.9-SNAPSHOT" is missing the following dependencies: Dependency "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MasterDataBean,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,module=mds-biz-ejb-1.1.9-SNAPSHOT,component=MDDValidatorBean,service=EjbEncFactory" is missing the following dependencies: Dependency "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MDDValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MDDValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' **") Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,module=mds-biz-ejb-1.1.9-SNAPSHOT,component=MasterDataBean,service=EjbEncFactory" is missing the following dependencies: Dependency "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' **") Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,module=mds-biz-ejb-1.1.9-SNAPSHOT,component=MasterDataXMLValidatorBean,service=EjbEncFactory" is missing the following dependencies: Dependency "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataXMLValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataXMLValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' **") Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,module=mds-biz-ejb-1.1.9-SNAPSHOT,component=RbacBean,service=EjbEncFactory" is missing the following dependencies: Dependency "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=RbacBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=RbacBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' **") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MDDValidatorBean,service=EJB3" is missing the following dependencies: Dependency "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MDDValidatorBean" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MDDValidatorBean' **") Dependency "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=MDDValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MDDValidatorBean,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MDDValidatorBean,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MasterDataBean,service=EJB3" is missing the following dependencies: Dependency "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataBean" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataBean' **") Dependency "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MasterDataBean,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MasterDataBean,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MasterDataXMLValidatorBean,service=EJB3" is missing the following dependencies: Dependency "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataXMLValidatorBean" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataXMLValidatorBean' **") Dependency "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataXMLValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MasterDataXMLValidatorBean,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=MasterDataXMLValidatorBean,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=RbacBean,service=EJB3" is missing the following dependencies: Dependency "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/RbacBean" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/RbacBean' **") Dependency "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=RbacBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described") Deployment "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=RbacBean,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:ear=mds-ear-1.1.9-SNAPSHOT.ear,jar=mds-biz-ejb-1.1.9-SNAPSHOT.jar,name=RbacBean,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") Deployment "jboss.web.deployment:war=/mds-console-web" is missing the following dependencies: Dependency "jboss-switchboard:appName=mds-ear-1.1.9-SNAPSHOT,module=mds-console-web-1.1.9-SNAPSHOT" (should be in state "Installed", but is actually in state "Deploy") DEPLOYMENTS IN ERROR: Deployment "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/RbacBean" is in error due to the following reason(s): ** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/RbacBean' ** Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=MDDValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" is in error due to the following reason(s): Described Deployment "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataXMLValidatorBean" is in error due to the following reason(s): ** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataXMLValidatorBean' ** Deployment "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MDDValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MDDValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' ** Deployment "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataXMLValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataXMLValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' ** Deployment "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataBean" is in error due to the following reason(s): ** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MasterDataBean' ** Deployment "org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MDDValidatorBean" is in error due to the following reason(s): ** NOT FOUND Depends on 'org.jboss.ejb.bean.instantiator/mds-ear-1.1.9-SNAPSHOT/mds-biz-ejb-1.1.9-SNAPSHOT/MDDValidatorBean' ** Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" is in error due to the following reason(s): Described Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataXMLValidatorBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" is in error due to the following reason(s): Described Deployment "jboss.ejb3:application=mds-ear-1.1.9-SNAPSHOT,component=RbacBean,module=mds-biz-ejb-1.1.9-SNAPSHOT,service=EjbEncFactory" is in error due to the following reason(s): Described Deployment "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=RbacBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=RbacBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' ** Deployment "jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataBean,module=mds-biz-ejb-1.1.9-SNAPSHOT" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:application=mds-ear-1.1.9-SNAPSHOT,component=MasterDataBean,module=mds-biz-ejb-1.1.9-SNAPSHOT' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:82) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.checkComplete(ProfileControllerContext.java:138) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:246) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95) [:0.2.2] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_22] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_22] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_22] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_22] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_22] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2951) regression: cannot compile return value "(java.lang.Object.class)"

by Wolfgang Laun (JIRA)

regression: cannot compile return value "(java.lang.Object.class)" ------------------------------------------------------------------ Key: JBRULES-2951 URL: https://issues.jboss.org/browse/JBRULES-2951 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical The rule below compiled with a version build from HEAD on February 10, 2011. But now: Unable to Analyse Expression target == source || target == (java.lang.Object.class): [Error: Failed to compile: 2 compilation error(s): - (1,32) unable to resolve method using strict-mode: ex10.Assignment.java() - (1,32) unqualified type in strict mode for: java] [Near : {... target == source || target == (java.lang.Object.class) ....}] ^ [Line: 1, Column: 32] : [Rule name='SameOrObjectIsAssignable'] ALSO please note that the line number is way off. rule SameOrObjectIsAssignable when $a: Assignment( $t: target, target == source || target == (java.lang.Object.class) ) then System.out.println( $a.toString() + " is OK. " ); retract( $a.getOriginal() ); end -- 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: (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, 9 months

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

6
10
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, 9 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, 9 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, 9 months

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