users@jersey.java.net

[Jersey] Quieting down some warnings

From: Christopher Piggott <cpiggott_at_gmail.com>
Date: Tue, 8 Mar 2011 16:49:27 -0500

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