Japp, will do. Ciao, Philipp Rossmanith
> -----Mensaje original----- > De: Guillaume Nodet [mailto:[EMAIL PROTECTED] > Enviado el: jueves, 15 de febrero de 2007 19:57 > Para: servicemix-dev@geronimo.apache.org > Asunto: Re: Default constructor for JBIContainer changes log level? > > Sure, commons-logging is configured. > Which in turns, starts log4j if included in the classpath. > By default, log4j will load a log4j.properties file ... > > And you're right. It seems that o.a.s.id.IdGenerator > calls the java.util.logging package. This is the only call > afaik and it should be removed. Can you raise a JIRA > for that ? > > On 2/15/07, Rossmanith, Philipp <[EMAIL PROTECTED]> wrote: > > > > P.s. JBIContainer doesn't seem to use org.apache.log4j, but makes calls > > to org.apache.commons.logging.Log and > > org.apache.commons.logging.LogFactory: > > >> > > private static final Log log = LogFactory.getLog(JBIContainer.class); > > << > > ... as well as to java.util.logging.Logger: > > >> > > public Logger getLogger(String suffix, String resourceBundleName) throws > > MissingResourceException, JBIException > > << > > > > Ciao, > > Philipp Rossmanith > > > > 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/ This e-mail may contain confidential or privileged information. Any unauthorised copying, use or distribution of this information is strictly prohibited.
