%l Pattern layout raises a protected property access error.
-----------------------------------------------------------

                 Key: LOG4PHP-17
                 URL: https://issues.apache.org/jira/browse/LOG4PHP-17
             Project: Log4php
          Issue Type: Bug
         Environment: log4php r692607,
PHP 5.2.4-2ubuntu5.3 with Suhosin-Patch 0.9.6.2,
Ubuntu 8.04
            Reporter: Yomei Komiya


When I use %l Pattern layout, an access error for LoggerLocationInfo->fullInfo 
occurred.

patches as follows.
------------------------------------------------------------------------------------------------
diff -urN log4php/helpers/LoggerPatternConverter.php 
log4php.new/helpers/LoggerPatternConverter.php
--- log4php/helpers/LoggerPatternConverter.php
+++ log4php.new/helpers/LoggerPatternConverter.php
@@ -367,7 +367,7 @@
         $locationInfo = $event->getLocationInformation();
         switch($this->type) {
             case LOG4PHP_LOGGER_PATTERN_PARSER_FULL_LOCATION_CONVERTER:
-                    return $locationInfo->fullInfo;
+                    return $locationInfo->getFullInfo();
             case LOG4PHP_LOGGER_PATTERN_PARSER_METHOD_LOCATION_CONVERTER:
                     return $locationInfo->getMethodName();
             case LOG4PHP_LOGGER_PATTERN_PARSER_LINE_LOCATION_CONVERTER:
diff -urN log4php/spi/LoggerLocationInfo.php 
log4php.new/spi/LoggerLocationInfo.php
--- log4php/spi/LoggerLocationInfo.php
+++ log4php.new/spi/LoggerLocationInfo.php
@@ -115,4 +115,12 @@
     {
         return ($this->methodName === null) ? LOG4PHP_LOGGER_LOCATION_INFO_NA 
: $this->methodName; 
     }
+
+    /**
+     *  Returns the full information of the caller.
+     */
+    public function getFullInfo()
+    {
+        return ($this->fullInfo === null) ? LOG4PHP_LOGGER_LOCATION_INFO_NA : 
$this->fullInfo;
+    }
 }
------------------------------------------------------------------------------------------------


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to