hmm, thats it. Actually it makes sense:
slf4j logging levels:
1. trace (the least serious)
2. debug
3. info
4. warn
5. error
6. fatal (the most serious)
jdk:
* SEVERE (highest value)
* WARNING
* INFO
* CONFIG
* FINE
* FINER
* FINEST (lowest value)
Mapping might be configurable in slf4j, but I wasn't able to find it
(yet). You might want to ask on slf4j mailing list about that.
Regards,
Pavel
On 03/09/2011 01:27 PM, Christopher Piggott wrote:
> Level.CONFIG huh, that's interesting. I'm using slf4j (actually,
> logback) which doesn't have such a level. It must be translating
> CONFIG to INFO.
>
>
> I'm using jersey-guice, so everything is served via GuiceFilter. This
> is all inside of Grizzly.
>
> Perhaps what I'm seeing is merely due to the logging configuration. I
> have a bunch of dependencies that use some combination of slf4j,
> j.c.l, j.u.l so I'm using slf4j to catch all of those and converge
> them into something sane. It works pretty well but perhaps this is
> one of the off-color side effects.
>
>
> On Wed, Mar 9, 2011 at 7:19 AM, Pavel Bucek<pavel.bucek_at_oracle.com> wrote:
>
>> Hello Christopher,
>>
>> which container do you use? And which jersey version?
>>
>> Why am I asking.. I looked to the source and I can see that these messages
>> should have Level.CONFIG, not INFO..
>>
>> And.. if you don't use ManagedBeans, CDI or EJB, you can disable these
>> loggers without any concerns, these are used only to report issues/errors
>> during initialization. And btw, this is not about maven dependencies, it is
>> more about container capabilities/support.
>>
>> Regards,
>> Pavel
>>
>>
>> On 03/08/2011 10:49 PM, Christopher Piggott wrote:
>>
>>> I would like to quit down some INFO level exceptions, but I don't want
>>> to turn them off if it's easy for me to just add some maven dependency
>>> that it's squawking about. I tried to figure out what these
>>> components are, but not being a hard core J2EE guy I'm not sure if
>>> that's the best idea (what if I suppress a log message that is
>>> actually meaningful?)
>>>
>>> Any thoughts on this stuff?
>>>
>>>
>>> 08 Mar 2011 16:29:18.381 INFO -
>>>
>>> com.sun.jersey.server.impl.managedbeans.ManagedBeanComponentProviderFactoryInitilizer
>>> The managed beans injection manager API is not available. JAX-RS
>>> managed beans support is disabled.
>>> javax.naming.NoInitialContextException: Need to specify class name in
>>> environment or system property, or as an applet parameter, or in an
>>> application resource file: java.naming.factory.initial
>>>
>>>
>>> 08 Mar 2011 16:29:18.379 INFO -
>>> com.sun.jersey.server.impl.cdi.CDIComponentProviderFactoryInitializer
>>> The CDI BeanManager is not available. JAX-RS CDI support is disabled.
>>> javax.naming.NoInitialContextException: Need to specify class name in
>>> environment or system property, or as an applet parameter, or in an
>>> application resource file: java.naming.factory.initial
>>>
>>>
>>> 08 Mar 2011 16:29:18.374 INFO -
>>> com.sun.jersey.server.impl.ejb.EJBComponentProviderFactoryInitilizer
>>> The EJB interceptor binding API is not available. JAX-RS EJB support
>>> is disabled.
>>> javax.naming.NoInitialContextException: Need to specify class name in
>>> environment or system property, or as an applet parameter, or in an
>>> application resource file: java.naming.factory.initial
>>>
>>>
>>>
>>
>>
>