Are you setting the content type of the response somewhere?
If not, you need to call
Note that "text/xml" is deprecated.
Good point. Thank you. We used "text/xml".
we have fixed, and we have rested, and that does not work.
We have the same issue.
Do you have any other idea ?
Are you setting the content type before generating the content itself? If part of the response has been committed you will no longer be able to set headers.
Different buffering behaviour between JBossWeb/Tomcat and Jetty would account for this difference.
thank you for your help. We have considered your comment and did an audit of the code.
And we have finally found in our custom framework a custom filter that added this the DOCTYPE.
This issue is solved.