Hi Philipp ! Can you point where this happen ? I don't recall any log4j direct calls in servicemix but the reconfiguration that happen in org.apache.servicemix.jbi.logging.LoggingService.
On 2/15/07, Rossmanith, Philipp <[EMAIL PROTECTED]> wrote:
Hi, I'm currently working on a DefaultBroker subclass (see http://www.nabble.com/Security-and-authorization-requirements-on-Request Broker-tf3135938s12049.html) in which I can add handlers processing MessageExchange instances within the sendExchangePacket method. One of them is a log4j-based logger with which I can log MessageExchange properties etc. I did a unit test based on the test cases for the SecuredBroker. After some investigations I found out that the call to the default constructor of the JBIContainer changes the level of the root logger to ERROR.*) Is this a desired behaviour, and how can I turn it off? Thanks in advance, Ciao, Philipp Rossmanith *) I observed the same behaviour in the original test case after adding a log4j Logger. This e-mail may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
