I believe it is the version number of the packet. Just manually change it to the version number that CFMX produces when it does CFWDDX and you should be apples.

If that works, write a script that changes the version number before CFMX imports.

Hope that helps,

-- geoff
http://www.daemon.com.au/

Rod Higgins wrote:
What does the WDDX packet look like?

Mark

Hi Mark,


I can't show you the contents of the packet but it is generated externally
and then uploaded to the server. Once uploaded the user manually runs the
xmlupload process to parse and insert the data into a db. The file format
has not changed and works fine for 4.51. It seems CFMX has a problem
parsing the file I am just writing some sample code to test if it is the
file itself or the upload procedure. At this stage I'm pretty certain it
is the file format causing the problem. Very annoying if that is the case.

Rod


Further to this problem. I uploaded a sample file via ftp to the server
and then ran this simple code below and I generated the same error. So it
is definitely a problem when parsing the wddx file. Now why would MM
change the format of the wddx file? Case sensitivity in the file format
perhaps?

Test code -:

<CFFILE ACTION="Read"
    FILE="#GetDirectoryFromPath(GetTemplatePath())#xmltest\naptest.xml"       
    VARIABLE="file">
<cfwddx action="WDDX2CFML" input=#file# output="data">




---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to