[jboss-jira] [JBoss JIRA] (JBLOGGING-86) Logger full class name issue in generated sources
Alessio Soldano (JIRA)
jira-events at lists.jboss.org
Tue Sep 18 06:11:35 EDT 2012
[ https://issues.jboss.org/browse/JBLOGGING-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated JBLOGGING-86:
-------------------------------------
Description:
I'm running the log file generation as described in https://community.jboss.org/wiki/JBossLoggingTooling#mavencompilerplugin (jboss-logging-processor 1.0.3.Final) and getting compile errors if the name of my @MessageLogger annotated interface name is Logger (regardless of the package).
Here is part of the generated source for an annotated class org.jboss.ws.api.Logger:
{code}
package org.jboss.ws.api;
...
@Generated(value = "org.jboss.logging.processor.model.MessageLoggerImplementor", date = "2012-09-18T11:56:34+0200")
public class Logger_$logger
extends DelegatingBasicLogger
implements Serializable, BasicLogger, org.jboss.ws.api.Logger
{
...
public Logger_$logger(final org.jboss.logging.Logger log) {
super(log);
}
public final void creatingUnifiedWebservicesDeploymentModel(final Object unit) {
super.log.logf(FQCN, (Logger.Level.TRACE), null, ((projectCode +"015503: ")+ creatingUnifiedWebservicesDeploymentModel$str()), unit);
}
{code}
Please note the "Logger.Level.TRACE" should actually be "org.jboss.logging.Logger.Level.TRACE"; the constructor parameter has the proper full class name specified instead.
was:
I'm running the log file generation as described in https://community.jboss.org/wiki/JBossLoggingTooling#mavencompilerplugin (jboss-logging-processor 1.0.3.Final) and getting compile errors if the name of my @MessageLogger annotated interface is Logger (regardless of the package).
Here is part of the generated source:
{code}
package org.jboss.ws.api;
...
@Generated(value = "org.jboss.logging.processor.model.MessageLoggerImplementor", date = "2012-09-18T11:56:34+0200")
public class Logger_$logger
extends DelegatingBasicLogger
implements Serializable, BasicLogger, org.jboss.ws.api.Logger
{
...
public Logger_$logger(final org.jboss.logging.Logger log) {
super(log);
}
public final void creatingUnifiedWebservicesDeploymentModel(final Object unit) {
super.log.logf(FQCN, (Logger.Level.TRACE), null, ((projectCode +"015503: ")+ creatingUnifiedWebservicesDeploymentModel$str()), unit);
}
{code}
Please note the "Logger.Level.TRACE" should actually be "org.jboss.logging.Logger.Level.TRACE"; the constructor parameter has the proper full class name specified instead.
> Logger full class name issue in generated sources
> -------------------------------------------------
>
> Key: JBLOGGING-86
> URL: https://issues.jboss.org/browse/JBLOGGING-86
> Project: JBoss Logging
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.1.2.GA
> Reporter: Alessio Soldano
> Assignee: David Lloyd
>
> I'm running the log file generation as described in https://community.jboss.org/wiki/JBossLoggingTooling#mavencompilerplugin (jboss-logging-processor 1.0.3.Final) and getting compile errors if the name of my @MessageLogger annotated interface name is Logger (regardless of the package).
> Here is part of the generated source for an annotated class org.jboss.ws.api.Logger:
> {code}
> package org.jboss.ws.api;
> ...
> @Generated(value = "org.jboss.logging.processor.model.MessageLoggerImplementor", date = "2012-09-18T11:56:34+0200")
> public class Logger_$logger
> extends DelegatingBasicLogger
> implements Serializable, BasicLogger, org.jboss.ws.api.Logger
> {
> ...
> public Logger_$logger(final org.jboss.logging.Logger log) {
> super(log);
> }
> public final void creatingUnifiedWebservicesDeploymentModel(final Object unit) {
> super.log.logf(FQCN, (Logger.Level.TRACE), null, ((projectCode +"015503: ")+ creatingUnifiedWebservicesDeploymentModel$str()), unit);
> }
> {code}
> Please note the "Logger.Level.TRACE" should actually be "org.jboss.logging.Logger.Level.TRACE"; the constructor parameter has the proper full class name specified instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list