Generating XML Output While Avoiding CFMX DevNet Watermark

The ColdFusion MX 6.1 DevNet Product Edition, available with a Macromedia DevNet Subscription, is a full Enterprise Edition version of ColdFusion MX 6.1 available to multiple IPs, but intended for development purposes only. Compare this to the Developer Edition which also has all Enterprise functionality, but is restricted to handling requests from just one IP address. The ColdFusion MX DevNet Edition license agreement does not permit using this edition in production, and at runtime the DevNet Edition injects a "watermark" into the generated output from a template. The watermarks can be seen as an additional META tag as shown here:

While this watermark does not adversely affect generated html output, it can break generated xml well-formedness if you're not careful. To avoid the watermark being added to generated xml output be sure to set the content-type to "text/xml" in your template. If you generate xml and output it without setting the content-type to "text/xml", then the xml will get the watermark and when the browser's built-in parser attempts to style the xml for display it will generate an error. The error provided by MSIE 6.02 is the following:

I've written this example which you can download and test yourself. The test has the following four options:

1. [ok] view generated xml from a cfm with content type set to type/xml (no watermark)



2. [error] view generated xml from a cfm without any content type set explicitly, which defaults to text/html (has watermark)



3. [ok] view xslt output of generated xml (has watermark)



4. [ok] view xml dump (has watermark)

If using a ColdFusion MX DevNet License, the solution for generating xml without the DevNet watermark is to set the content type to text/xml. The solution for generating plaintext files without the DevNet watermark is to set the content type to text/plain.

Download Example (doesn't work in cfmx 7 as is)

Available as Technote

Comments