I think the DefaultHandler may be an issue. I see some "special" code in there for "instanceof DefaultHandler" so I'm curious what would happen if you removed that. :-)
Dan On Mon September 28 2009 11:03:06 am Jim Talbut wrote: > Hi, > > Continuing with my Jetty servers inside Tomcat I've been trying to get > request logging working on the Jetty side. > > I've got this in my beans.xml: > <httpj:engine-factory bus="cxf" id="jetty-factory"> > <httpj:engine port="8009"> > <httpj:tlsServerParametersRef id="secure" /> > <httpj:threadingParameters minThreads="1" maxThreads="5" /> > <httpj:handlers> > <bean class="org.mortbay.jetty.handler.RequestLogHandler" > > <property name="requestLog"> > <bean class="org.mortbay.jetty.NCSARequestLog"> > <property name="filename" > value="/usr/share/apache-tomcat/logs/jetty-request.log.yyyy_mm_dd"/> > </bean> > </property> > </bean> > <bean class="org.mortbay.jetty.handler.DefaultHandler"/> > </httpj:handlers> > </httpj:engine> > </httpj:engine-factory> > > but I'm not clear on where CXF fits in with these handlers. > > Every response that the logger sees has a response code > (response.getStatus()) of 200, even though the client is seeing a 404. > So I'm thinking that my handler is somehow installed incorrectly > alongside whatever CXF does. > Any clues? > > Additionally, is the DefaultHandler needed or will CXF take care of 404s? > > Thanks. > > Jim > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > -- Daniel Kulp [email protected] http://www.dankulp.com/blog
