Re: Response for a 405 can't be parsed by SAX

Thanks for the replies guys. I definitely don't need to parse it as XML, I'm using XMLUnit in my integration testing to compare the responses (my service returns XML entities). Also, our QA tell prefers to compare XML. So I wasn't pointing it out as a shortcoming by any means, just raising

Re: Response for a 405 can't be parsed by SAX

Hi Rhett, SAX can't parse it because it's HTML, not XML. (br alone is valid HTML.) You should be able to determine whether it is HTML or XML in your client by examining the content type header. Is restlet not setting that header correctly? If you want to provide XML-formatted error

Re: Response for a 405 can't be parsed by SAX

Hi Stephan, On Jun 13, 2009, at 3:45 PM, Stephan Koops wrote: Hi Rhett, Hello Everyone, I had a question about the 405 response message returned by Restlet 1.1.1. When I try a parse the XML response, I get the following: [Fatal Error] :8:3: The element type br must be terminated by

Response for a 405 can't be parsed by SAX

Hello Everyone, I had a question about the 405 response message returned by Restlet 1.1.1. When I try a parse the XML response, I get the following: [Fatal Error] :8:3: The element type br must be terminated by the matching end-tag /br. The entire response: html head titleStatus

Re: Response for a 405 can't be parsed by SAX

Hi John, On Jun 12, 2009, at 10:10 AM, John Prystash wrote: Hello Everyone, I had a question about the 405 response message returned by Restlet 1.1.1. When I try a parse the XML response, I get the following: [Fatal Error] :8:3: The element type br must be terminated by the