Hey,
the class property $mdcCopyLookupRequired (LoggerLoggingEvent:77) is
unused. Do we need it yet, or can it be deleted?
regards,
Florian
not access private property LoggerLoggingEvent::$fqcn
> -
>
> Key: LOG4PHP-124
> URL: https://issues.apache.org/jira/browse/LOG4PHP-124
> Project: Log4php
>
: 2.1
> Cannot access private property LoggerLoggingEvent::$fqcn
> -
>
> Key: LOG4PHP-124
> URL: https://issues.apache.org/jira/browse/LOG4PHP-124
> Project: Log4php
>
ess private property LoggerLoggingEvent::$fqcn
> -
>
> Key: LOG4PHP-124
> URL: https://issues.apache.org/jira/browse/LOG4PHP-124
> Project: Log4php
> Issue Type: Bug
>
self too :-)
> Cannot access private property LoggerLoggingEvent::$fqcn
> -
>
> Key: LOG4PHP-124
> URL: https://issues.apache.org/jira/browse/LOG4PHP-124
> Project: Log4php
>
tter method - there more descriptive name can
never hurt :)
> Cannot access private property LoggerLoggingEvent::$fqcn
> -
>
> Key: LOG4PHP-124
> URL: https://issues.apache.org/jira
than getFullQualifiedClassName()
I just meant: write it out
Whats you opinion on that?
And yes, I am also looking forward to a new release without -incubating - lets
discuss it on the mailinglist, ok?
> Cannot access private property LoggerLoggingEvent
reat :) Apropos public, what about a new release which would also get rid of
this "-incubating" suffix that still makes the downloadable files look somewhat
"BETA" and might discourage people from using them.
> Cannot access private propert
private property LoggerLoggingEvent::$fqcn
> -
>
> Key: LOG4PHP-124
> URL: https://issues.apache.org/jira/browse/LOG4PHP-124
> Project: Log4php
> Issue Type: Bug
> Compo
($event) {
- return $event->fqcn;
+ return $event->getFqcn();
}
}
> Cannot access private property LoggerLoggingEvent::$fqcn
> -
>
> Key: LOG4PHP-124
> URL: https://i
Cannot access private property LoggerLoggingEvent::$fqcn
-
Key: LOG4PHP-124
URL: https://issues.apache.org/jira/browse/LOG4PHP-124
Project: Log4php
Issue Type: Bug
is already fixed in the 2.0 release
> undefined method getLoggerRepository() in LoggerLoggingEvent
>
>
> Key: LOG4PHP-84
> URL: https://issues.apache.org/jira/browse/LOG4PHP-84
>
should fix this for 2.0
> undefined method getLoggerRepository() in LoggerLoggingEvent
>
>
> Key: LOG4PHP-84
> URL: https://issues.apache.org/jira/browse/LOG4PHP-84
>
view!
> undefined method getLoggerRepository() in LoggerLoggingEvent
>
>
> Key: LOG4PHP-84
> URL: https://issues.apache.org/jira/browse/LOG4PHP-84
> Project: Log4php
>
[
https://issues.apache.org/jira/browse/LOG4PHP-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Grobmeier updated LOG4PHP-84:
---
Fix Version/s: 2.1
> undefined method getLoggerRepository() in LoggerLoggingEv
in LoggerLoggingEvent
>
>
> Key: LOG4PHP-84
> URL: https://issues.apache.org/jira/browse/LOG4PHP-84
> Project: Log4php
> Issue Type: Bug
> Components: Code
&g
debug("Now comes the current MyClass object:");
$logger->debug($person);
$ cat src/examples/resources/renderer_map.properties
log4php.renderer.Person = PersonRenderer
log4php.appender.default = LoggerAppenderEcho
log4php.appen
undefined method getLoggerRepository() in LoggerLoggingEvent
Key: LOG4PHP-84
URL: https://issues.apache.org/jira/browse/LOG4PHP-84
Project: Log4php
Issue Type: Bug
Patched.
Thank You.
-Marco
- Original Message -
From: "Knut Urdalen" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 30, 2005 12:20 AM
Subject: Serializing LoggerLoggingEvent: Missing timestamp
> Since I can't find any bug report database for log4php
Since I can't find any bug report database for log4php I'll post this to
the developer list.
LoggerAppenderSocket with useXml = false will serialize a
LoggerLoggingEvent over the network socket. Unserializing the logging
event on the other side I found that timestamp was missing. Ch
20 matches
Mail list logo
