Burlap Stacktrace

[Erik Pragt]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi all,

 

I'm currently developing a Burlap/Eclipse RCP application, and every time the Burlap proxy starts, it first does a GET, followed by a POST (the actual request). This behaviour is as designed by the Burlap library, and it's nothing I can do about. The GET request, however, is caught by the Spring library and is causing an enormous stacktrace in the log each time a burlap call is made. According to Juergen Hoeller, this behaviour has been fixed in Spring 2.5.3. Grails is using Spring 2.5.1, so I upgraded Grails to use Spring 2.5.3. There's, however,  no difference in the the behaviour: Grails/Spring still displays a huge stacktrace.

 

My question is: has Grails registered a special HandlerExceptionResolver (or anything else) to display this stacktrace?

 

You can see the stacktrace and the discussion I had with Juergen here: http://jira.springframework.org/browse/SPR-4542

 

Thanks, Erik

[Peter Ledbrook-2]

2008/5/3 Erik Pragt <erik@...>:

>
>
> Hi all,
>
> I'm currently developing a Burlap/Eclipse RCP application, and every time
> the Burlap proxy starts, it first does a GET, followed by a POST (the actual
> request). This behaviour is as designed by the Burlap library, and it's
> nothing I can do about. The GET request, however, is caught by the Spring
> library and is causing an enormous stacktrace in the log each time a burlap
> call is made. According to Juergen Hoeller, this behaviour has been fixed in
> Spring 2.5.3. Grails is using Spring 2.5.1, so I upgraded Grails to use
> Spring 2.5.3. There's, however,  no difference in the the behaviour:
> Grails/Spring still displays a huge stacktrace.
>
> My question is: has Grails registered a special HandlerExceptionResolver (or
> anything else) to display this stacktrace?

I suspect that the problem is with the way Grails uses
DispatcherServlet: it extends it and overrides some rather important
methods. This means that some changes to Spring's DispatcherServlet
will not propagate to Grails. I'm not familiar enough with
GrailsDispatcherServlet at the moment to refactor it, but we certainly
need to customise the servlet in a cleaner fashion.

Cheers,

Peter

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Erik Pragt]

>> My question is: has Grails registered a special HandlerExceptionResolver
>> (or
>> anything else) to display this stacktrace?
>
> I suspect that the problem is with the way Grails uses
> DispatcherServlet: it extends it and overrides some rather important
> methods. This means that some changes to Spring's DispatcherServlet
> will not propagate to Grails. I'm not familiar enough with
> GrailsDispatcherServlet at the moment to refactor it, but we certainly
> need to customise the servlet in a cleaner fashion.

Hi Peter,

Okay, thanks for the reply! I'll see if I can find some time to look into it
(no promises! ;-), since this problem is rather annoying!

Erik


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email