On Aug 9, 2009, at 1:59 PM, Paul Sandoz wrote:
> Hi,
>
> I looked briefly into this and it should be rather easy to modify,
> but i have one question.
>
> Do people think it appropriate log the request and response
> entities? There is no way to stream out the entities, so it requires
> that they are buffered as String instances. For large requests/
> responses this may be problematic but perhaps that is the cost of
> logging? also there could be a feature to turn off entity logging.
>
This is fixed in the trunk (JavaDoc below).
Client side will be fixed tomorrow.
Paul.
/**
* A logging filter.
* <p>
* The request headers, request entity, response headers and response
entity
* will be logged. By default logging will be output to System.out.
* <p>
* When an application is deployed as a Servlet or Filter this Jersey
filter can be
* registered using the following initialization parameters:
* <blockquote><pre>
* <init-param>
* <param-
name>com.sun.jersey.spi.container.ContainerRequestFilters</param-
name>
* <param-
value>com.sun.jersey.api.container.filter.LoggingFilter</param-
value>
* </init-param>
* <init-param>
* <param-
name>com.sun.jersey.spi.container.ContainerResponseFilters</
param-name>
* <param-
value>com.sun.jersey.api.container.filter.LoggingFilter</param-
value>
* </init-param>
* </pre></blockquote>
* <p>
* The logging of entities may be disabled by setting the feature
* {_at_link #FEATURE_LOGGING_DISABLE_ENTITY} to true. When an
application is
* deployed as a Servlet or Filter this Jersey filter can be
* registered using the following initialization parameter:
* <blockquote><pre>
* <init-param>
* <param-
name>com.sun.jersey.config.feature.logging.DisableEntitylogging</
param-name>
* <param-value>true</param-value>
* </init-param>
* </pre></blockquote>
*
* @author Paul.Sandoz_at_Sun.Com
* @see com.sun.jersey.api.container.filter
*/