Everybody says this, but they don't read the problem.  This is in he WDDX
output by the CFMX server when a CFC is called remotely.  I am NOT
generating this myself so I cannot put the content=XML in the page.  As I
said in my post.

-----Original Message-----
From: Marlon Moyer [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 25, 2004 11:40 AM
To: CF-Talk
Subject: RE: Turning DevNet CFMX into Developer?

if you put a <cfcontent type="text/html"> at the top of your page, it will
suppress the watermark.

http://www.macromedia.com/support/coldfusion/ts/documents/devnet_watermark.h
tm

Marlon

-----Original Message-----
From: Craig Earls [mailto:[EMAIL PROTECTED]
Sent: Sun 4/25/2004 9:03 AM
To: CF-Talk
Cc:
Subject: Turning DevNet CFMX into Developer?
I am making use of WDDX output from CFCs to allow some _javascript_ routines
to call home.  They work fine in production, but because the DevNet CFMX
sever sticks a silly watermark into every outgoing file it breaks the WDDX
parsing.  I know about setting the output type to XML for XML I generate,
but evidently the folks at MM don't know about it since they didn't do it in
the WDDX generation code.

Is there anyway around that? I figure I could turn my DevNet installation
into a developer edition for testing (I am an Army of One) and that would
get rid of the watermark in the WDDX output.  Does anyone have any other
ideas?
  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to