-----BEGIN PGP SIGNED MESSAGE-----
Florent Guillaume wrote:
> Dieter Maurer <[EMAIL PROTECTED]> wrote:
> [about getObject logging missing objects]
>>>Yes, logging should be there. I'll add a LOG at level WARNING somewhere,
>>>I'm not sure where (after all it's unrestrictedTraverse that does the
>>When something in the catalog tells you, there were an object
>>and the object is not locatable, then this is an ERROR
>>and not a WARNING -- because, you met a data inconsistency.
>>Data inconsistencies are serious enough to be classified as "ERROR".
> Let's not go into too much semantics here. Note that WARNING is an alias
> of PROBLEM. zLOG defines these levels as:
> PROBLEM=100 -- This isn't causing any immediate problems, but deserves
> ERROR=200 -- This is going to have adverse effects.
> And indeed the missing object isn't causing immediate problems.
Exactly. The point is that the "adverse effect" *already happened*, in
some prior request, probably due to one of Chris' beloved hasattrs ;).
The current request should *not* be prevented from continuing.
Chris, take this as a fiat: this one will *never* turn into an exception.
Tres Seaver [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests