--On 14. Juni 2006 10:25:57 +0200 thomas desvenain <thomas.desvenain@gmail.com> wrote:
2006/6/13, Chris McDonough <chrism@plope.com>:
I suppose a log call is fine.
I *really* like these messages, because they catch a lot of my own boneheaded security declaration errors. But for ones that aren't actually "real" problems (like the ones shown by the OP), it would be nice to be able to filter them away at startup, especially when starting in the foreground or running "zopectl debug" or "zopectl test". Making these into actual warnings.warn calls would let us do that with a warnfilter, but any other solution would be fine as well.
In my way those messages can be usefull for everybody... but not at every time it would be nice to get a tool (using regexp) to adapt them to our present needs (installing a product, developping a product on a test instance for example)
From the practical point of view: just close your eyes. When you run a server in production you will see those messages only in the logs. If you are a developer you should be aware of the content of the messages and fix your own code or upgrade the related products.
-aj