Jboss7 add the DOCTYPE in xml Response

[fabien.t]

Hi all,

The jboss7 add the DOCTYPE in the xml response through the an HTML stream.

The application generate a response as :

<?xml version="1.0" encoding="UTF-8"?>
<orderResponse xmlns="http://www.wolrd.com/application/delivery/2.0">
   <status>OK</status>
   <order transactionId="123">
      <orderedProductsList>
         <product proprietaryId="123">
            <url usageType="PermanentDownload" distributionType="Internet">http://Application.world.com/978156790a400202590ed49d03f5725f/ici.acsm</url>
         </product>
      </orderedProductsList>
   </order>
</orderResponse>

This response is sent is the outputstream and jboss7 send :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE orderResponse
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<orderResponse xmlns="http://www.wolrd.com/application/connectedcms/delivery/2.0">
   <status>OK</status>
   <order transactionId="123">
      <orderedProductsList>
         <product proprietaryId="123">
            <url usageType="PermanentDownload" distributionType="Internet">http://Application.world.com/978156790a400202590ed49d03f5725f/ici.acsm</url>
         </product>
      </orderedProductsList>
   </order>
</orderResponse>

Why jboss7 added the DOCTYPE ? We have tested the application on jetty, and we do not have this issue. How i can fix that ?

I am working with JBoss 7:

- Modules version 1.1.1.GA

- JBoss MSC version 1.0.2.GA

- JBoss AS 7.1.1.Final "Brontes"

bests regards,

fabien

[sfcoy]

Are you setting the content type of the response somewhere?

If not, you need to call

response.setContentType("application/xml");

Note that "text/xml" is deprecated.

[fabien.t]

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 ?

[sfcoy]

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.

[fabien.t]

Hello,

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.

Thank you.

fabien