--- Den fre 24/7/09 skrev Paul Sandoz <Paul.Sandoz@Sun.COM>:
> > I am using Sun's HTTPSERVER
> >
>
> Hmm... the Jersey LW HTTP HttpHandlerContainer is written
> such that an IOException will be thrown from the handle
> method. I suspect that when the status code and headers are
> set such exceptions do not result in premature termination
> of the connection (plus no logging occurs).
If I understand you correctly, then Jersey sets the status code prematurely (before it is sure that no exceptions are throw in JAXB) ?
> If you don't have any specific configuration with that
> container it is easy to switch to using Grizzly to verify if
> you get the same behaviour.
Actually, it is quite some work for me to switch as I am using HTTPServer internally as an very light-weight embedded web server. I am not using servles, war files or the std j2ee structure. However eventually, I may have to switch to another embedded web server anyway as I would like to support digest authentication. It will take some time though.
Would it be helpful if I instead create a small hello-world-style example that reproduce the problem for you (I can properly do so in a day or so if needed) ? And if I do, what is the chance it can be fixed for jersey 1.1.2 (as it is highly annoying and actually a "crime" to swallow exceptions and return success :-))
Cheers,
Morten
________________________________________________________
Audi, Fiat, Peugeot, Skoda, Porsche, Toyota, Ford - Kelkoo har brugte biler til en hver smag! Klik her for at sammenligne priser.(
http://dk.yahoo.com/r/pat/mmb)