[jboss-jira] [JBoss JIRA] (SECURITY-886) Upgrade jboss-logging-processor

Philippe Marschall (JIRA) issues at jboss.org
Sun May 17 13:52:19 EDT 2015


Philippe Marschall created SECURITY-886:
-------------------------------------------

             Summary: Upgrade jboss-logging-processor
                 Key: SECURITY-886
                 URL: https://issues.jboss.org/browse/SECURITY-886
             Project: PicketBox 
          Issue Type: Component  Upgrade
          Components: Picketbox5
            Reporter: Philippe Marschall
            Assignee: Stefan Guilhen


Versions of jboss-logging-processor 1.1.0.Final and later generate much more efficient code.

This is how the generated code by 1.0.0.Final looks like:
{code}
    public final void debugEJBPolicyModuleDelegateState(final String methodName, final String interfaceName, final String requiredRoles) {
        super.log.logf(FQCN, (Logger.Level.DEBUG), null, ((projectCode +"000291: ")+ debugEJBPolicyModuleDelegateState$str()), methodName, interfaceName, requiredRoles);
    }
{code}
As you can see from {{(projectCode +"000291: ")+ debugEJBPolicyModuleDelegateState$str()}} it still allocates new strings even if debug logging is not on.

This is how the generated code by 1.1.0.Final and later looks like:
{code}
    public final void debugEJBPolicyModuleDelegateState(final java.lang.String methodName, final java.lang.String interfaceName, final java.lang.String requiredRoles) {
        super.log.logf(FQCN, (org.jboss.logging.Logger.Level.DEBUG), null, debugEJBPolicyModuleDelegateState$str(), methodName, interfaceName, requiredRoles);
    }
{code}
No more new strings are allocated.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jboss-jira mailing list