Hi, if you can share something that's clearly better.
I think both are linked and if someone catches the exception before you it sets the http code. the question is who? maybe tomcat hope you can reproduce it easily to make a step forward - Romain 2012/6/1 tom <[email protected]> > Hi, > > I stumbled upon two behaviors and I wonder whether these are intended or > not. > > So here is the first problem: > > In one of my projects I got a Filter that is supposed to take care of the > error handling. So it sets appropiate HTTP Status Codes in the response. > The > thing is that the response is already committed when it "leaves" the > servlet > and thus I can't change the status anymore. > > Is there a way to change that? Or am I trying to do something that is not > intended on TomEE? > > The second problem occurs also in that error handling Filter. > > It basically is a giant try-catch block. It trys the filtercain.doFilter() > method and the servlet methods throw exceptions, which are supposed to get > handled in that filter. Unfortunately the Exceptions get caught somewhere > before they reach the filter. > > Again: Can I change that? > > Hopefully the provided information lead to a solution, since the problems > occur in an enterprise projects which I can't realy show. > > If not I'll try to rebuild this behavior in a sample project. > > Thanks in advance :) > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/When-does-TomEE-commit-a-response-and-are-exceptions-caught-before-they-reach-a-filter-tp4655297.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
