1 Reply Latest reply on Aug 26, 2008 10:24 AM by stalep



      after looking into JBAOP-623 ive changed our logger to something similar to what messaging got. i havent changed the logic for when we apply our own logger (which is SystemOutLoggerPlugin), and the problem that i see is that its not applied at all when aop is running standalone.
      when i run in "verbose" mode standalone i usually get:

      [java] log4j:WARN No appenders could be found for logger (org.jboss.aop.instrument.InstrumentorFactory).
       [java] log4j:WARN Please initialize the log4j system properly.

      this is something we should set by if its not set by the user imo.
      - but i guess we cant always set org.jboss.logging.Logger.pluginClassName to our own logger since this would overwrite what others has set it to (correct me if im wrong here).

      we also have a lot of System.err.print outputs in our code, should i change them to use the logger too or is it a good reason why its not using the logger? :)

        • 1. Re: AOPLogging

          ill just end up checking if the actual delegateplugin is NullLoggerPlugin. if it is we'll use our own SystemLoggerPlugin.
          - and ill change all the:


          to use logger.