Uploaded image for project: 'PicketBox '
  1. PicketBox
  2. SECURITY-886

Upgrade jboss-logging-processor

XMLWordPrintable

    • Icon: Component Upgrade Component Upgrade
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • PicketBox
    • None

      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:

          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);
    }

      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:

          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);
    }

      No more new strings are allocated.

              sguilhen Stefan Guilhen
              pmarscha Philippe Marschall (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: