Hi,
Tracing is now implemented in 1.1.5-ea-SNAPSHOT. See:
http://blogs.sun.com/sandoz/entry/tracing_in_jersey
There are still some areas where traces need to be added. Specifically
for exception mapping (and perhaps context resolving).
Paul.
On Nov 25, 2009, at 3:10 PM, Paul Sandoz wrote:
> Hi,
>
> See attached for a quick example of a prototype. I am using the
> Bookstore example. Notice that it presents the list of regular
> expressions to be matched (in matching order) as well as the JSP
> file that was resolved and the message body writer that utilized.
>
> Obviously these messages need to be improved, but hopefully this
> gets the point across. I need to work out an appropriate compact but
> informative syntax.
>
> It should be easy to also generate HTML responses as well for when
> 4/5xx errors occur.
>
> Paul.
>
>
> <pastedGraphic.tiff>
> On Nov 24, 2009, at 11:41 AM, Paul Sandoz wrote:
>
>> Hi,
>>
>> Many ideas in Jersey/JAX-RS were inspired by Stapler the underlying
>> HTTP-based framework utilized by Hudson.
>>
>> Here is another potential idea. Stapler has a trace mode:
>>
>> http://wiki.hudson-ci.org/display/HUDSON/Figuring+out+URL+binding+of+Stapler
>>
>> Please let me know if you would like such a feature in Jersey.
>>
>> I think this is a more promising approach rather than explicit
>> logging on the server side, and the of course the response could be
>> logged using the LoggingFIlter thus exposing trace headers.
>>
>> Paul.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net