displaying top 100 results
Tracker Issue WDDX Serialization of date objects is broken
WDDX Serialization of date objects is broken
Comment on WDDX Serialization of date objects is broken by Jeff C.
Comment on WDDX Serialization of date objects is broken by Sean C.
Comment on WDDX Serialization of date objects is broken by Nitin K.
WDDX Date time Serialize truncates time with +1 in German time zone
2673579 CF-4126385 Aaron N. Hi Adobe,
1) WDDX should serialize/deserialize ordered struct
2) If sorted struct was created WITHOUT closure, WDDX should serialize/deserialize the sorted struct
3) If sorted struct was created WITH closure, it should be documented that it will be serialized
Tracker Issue incorrect serialization of undefined values.
6843429 CF-4207281 Language : WDDX Serialization incorrect serialization of undefined values. Problem Description:
the wddx serialization process converts undefined values to null, which in turn get deserialized to an empty string, so undefined values do not stay undefined.
Steps to Reproduce
Tracker Issue incorrect serialization of undefined values.
6843289 CF-4207280 Language : WDDX Serialization incorrect serialization of undefined values. Problem Description:
the wddx serialization process converts undefined values to null, which in turn get deserialized to an empty string, so undefined values do not stay undefined.
Steps to Reproduce
Tracker Issue incorrect serialization of undefined values.
6843288 CF-4207279 Language : WDDX Serialization incorrect serialization of undefined values. Problem Description:
the wddx serialization process converts undefined values to null, which in turn get deserialized to an empty string, so undefined values do not stay undefined.
Steps to Reproduce
Tracker Issue [ANeff] Bug for: WDDX mangles ordered struct
2673579 CF-4126385 Language Aaron Neff [ANeff] Bug for: WDDX mangles ordered struct WDDX mangles ordered struct
Repro:
orderedStruct = [b="b", a="a", c="c"];
cfwddx(action="cfml2wddx", input=orderedStruct, output="serializedStruct");
cfwddx(action="wddx2cfml", input=serialized
Tracker Issue Bug 76746:(Watson Migration Closure)datetime conversion to/from WDDX doesn't honor DST
2601144 CF-3038277 Language : WDDX Serialization PaulH Bug 76746:(Watson Migration Closure)datetime conversion to/from WDDX doesn't honor DST Problem:
datetime conversion to/from WDDX doesn't honor DST.
Method:
Krishna 5/20/09:Repro steps
1.Change the system Time zone to GMT -8:00(US
2598901 CF-3040812 Language : WDDX Serialization Rob Parkhill Bug 81726:Taking a query object and converting it to WDDX using the following code:which is then inserted into the database (which works fine). However when reading the data out of the database and converting back to WDDX - using
2608403 CF-4101845 Language : WDDX Serialization Aaron Neff [ANeff] Bug for: input containing XML object breaks cfwddx input containing XML object breaks cfwddx
Repro:
foo
Actual result: exception "Object Type coldfusion.xml.XmlNodeList is not supported for this operation. Pass object
4259697 CF-4202189 Language : Serialization [ANeff] Bug for: WDDX (correct) vs JSON (incorrect) wrt DateTime Issue: WDDX (correct) vs JSON (incorrect) wrt DateTime
Repro:
WDDX gets it right (maintains UTC offset and deserializses back to DateTime):
myDateTime = createDate(2018,1,1)
cfwddx
Tracker Comment Comment on Bug 76746:(Watson Migration Closure)datetime conversion to/from WDDX doesn't honor DST by Aaron N.
.runtime.OleDateTime value serialized to WDDX and then deserialized back again is the same regardless of OS/JVM tz/DST.
Thanks!,
-Aaron
Comment on [ANeff] Bug for: WDDX mangles ordered struct by Nikhil D.
Tracker Comment Comment on [ANeff] Bug for: WDDX (correct) vs JSON (incorrect) wrt DateTime by Aaron N.
Comment on [ANeff] Bug for: WDDX (correct) vs JSON (incorrect) wrt DateTime by Aaron N.
Tracker Comment Comment on [ANeff] Bug for: WDDX (correct) vs JSON (incorrect) wrt DateTime by Aaron N.
Comment on [ANeff] Bug for: WDDX (correct) vs JSON (incorrect) wrt DateTime by Aaron N.
Tracker Comment Comment on [ANeff] Bug for: WDDX (correct) vs JSON (incorrect) wrt DateTime by Immanuel N.
Comment on [ANeff] Bug for: WDDX (correct) vs JSON (incorrect) wrt DateTime by Immanuel N.
2597415 CF-3043877 Language : WDDX Serialization Raymond Camden Bug 86957:(Watson Migration Closure)If you take an array, convert it to WDDX, then convert it back to CFML, you can't arrayResize it Problem:
If you take an array, convert it to WDDX, then convert it back to CFML, you can't array
2672764 CF-4172952 Language : WDDX Serialization Aaron Neff [ANeff] Bug for: CF11 vs CF2016 - cfwddx now throws StackOverflow when using extends In CF11, serializeJSON(local) and cfwddx(action="cfml2wddx", input=local, ..) skip serialization of THIS scope - even if CFC extends another CFC. Good
2608238 CF-4158658 Language : Serialization Aaron Neff [ANeff] Bug for: CF11+ broke deserialization of WDDX'd timestamp query columns CF11+ broke deserialization of WDDX'd timestamp query columns
Steps to reproduce:
1) Run this code in CF10, CF11 and CF2016:
Actual result: CF10 displays
2608237 CF-4158660 Language : Serialization Aaron Neff [ANeff] Bug for: incorrect deserialization of WDDX'd bit column incorrect deserialization of WDDX'd bit column
Steps to reproduce:
1) Run this code in CF10, CF11 and CF2016:
Actual result: Deserialization
Tracker Issue Bug 83819:WDDX fails to parse a form object correctly when one of the fields contains an &
2597969 CF-3041885 Language : WDDX Serialization Fred Valone Bug 83819:WDDX fails to parse a form object correctly when one of the fields contains an & Problem:
WDDX fails to parse a form object correctly when one of the fields contains an &
Method:
create a form with a few fields one of them a
2608403 CF-4101845 Aaron N. Hi Adobe,
I'm glad to see this is "Needs Review".
Each time cfml2wddx touches an XML var, it should toString() it. That resolves the issue.
Currently, cfml2wddx throws an exception on XML vars. That isn't useful for already-existing code having complex nested
in a real database. Database NULLs have always been returned to CF as empty string, and empty string passes through serialization unchanged. Round trip serialization/deserialization works fine using WDDX, in that both empty string and NULL db values are treated as empty string before and after
in a real database. Database NULLs have always been returned to CF as empty string, and empty string passes through serialization unchanged. Round trip serialization/deserialization works fine using WDDX, in that both empty string and NULL db values are treated as empty string before and after
in a real database. Database NULLs have always been returned to CF as empty string, and empty string passes through serialization unchanged. Round trip serialization/deserialization works fine using WDDX, in that both empty string and NULL db values are treated as empty string before and after
Tracker Comment Comment on Wishlist by Aaron N.
of new functions added [StructSort() could've been enhanced instead of adding StructToSorted()])
2) Improved JSON serialization (I'd like to see a JSON serialization/deserialization of query that maintains column type - this is an advantage of WDDX)
3) Decrypt CF Admin (basically, overhaul CF Admin
2836798 CF-4198325 Language : Serialization Aaron Neff [ANeff] ER for: SerializeJSON(query, "row|column") to preserve column type Issue: When deserializing a WDDX'd query, there is column type information (good). When deserializing a .toJSON()'d query, there is no column type information (bad
Tracker Issue [ANeff] Bug for: THIS.searchImplicitScopes=false breaks web service argumentCollection
Arg="foobar"};
cfhttp(url='http://' & CGI.HTTP_HOST & getDirectoryFromPath(CGI.SCRIPT_NAME) & 'MyCFC.cfc?method=myFunction&argumentCollection=' & serializeJSON(myArgs).encodeForURL() & '&returnFormat=json');
writeOutput(CFHTTP.FileContent);//returns {"MYARG":null} (bad)
cfwddx(action="cfml2wddx", input
administrator, neo-cron.xml should be replaced with empty (and valid) file.
- or - at least... we should see something like 'XML (WDDX) parse error in neo-cron.xml'...
in the context of the CF administrator (where access is nominally limited to appropriate/knowledgeable people)... the corrupted file should