Those are all from Jetty.
Looking at it, it looks like they are using slf4j for logging
(http://www.slf4j.org). Looking at the site, I see:
http://fernandoribeiro.eti.br/2006/05/24/how-to-use-slf4j-with-log4j/
so it looks like you just need to put their slf4j-log4j.jar on the
classpath. Not really sure though as I'm not very familiar with slf4j.
Dan
On Tuesday 25 September 2007, Holger Stolzenberg wrote:
In my project I am using log4j.
I have configured it to log the cxf packages with level warn. Nearly
everything is fine. There are some outputs that are written to
'System.out' I think and therefore they are always printed out (e.g.
during maven build tests). Below are examples of the messages that are
always printed out.
25.09.2007 13:15:24
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass INFO: Creating Service
{http://backend.shop.eex.com/ws-api}CouponService from class
com.ewerk.eex.shop.backend.wsapi.coupon.CouponServiceImpl
25.09.2007 13:17:27 sun.reflect.NativeMethodAccessorImpl invoke0
INFO: Logging to org.slf4j.impl.JDK14LoggerAdapter(org.mortbay.log)
via org.mortbay.log.Slf4jLog 25.09.2007 13:17:27
sun.reflect.NativeMethodAccessorImpl invoke0 INFO: jetty-6.1.0
25.09.2007 13:17:27 sun.reflect.NativeMethodAccessorImpl invoke0
INFO: Started SelectChannelConnector @ 0.0.0.0:8080
How can I get rid of this messages ???
Mit lieben Grüßen aus dem eWerk
| Holger Stolzenberg
| Softwareentwickler
|
| Geschäftsführer:
| Frank Richter, Erik Wende, Hendrik Schubert
|
| eWerk IT GmbH
| Markt 16
| Leipzig 04109
| http://www.ewerk.com
| HRB 9065, AG Leipzig
| Hauptniederlassung Leipzig
|
| fon +49.341.4 26 49-0
| fax +49.341.4 26 49-88
| mailto:[EMAIL PROTECTED]
|
| Support:
| fon 0700 CALLME24 (0700 22556324)
| fax 0700 CALLME24 (0700 22556324)
|
| Auskünfte und Angebote per Mail
| sind freibleibend und unverbindlich.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
