On Thu, Dec 16, 2010 at 07:54, Fink, Andreas <[email protected]> wrote:
Hi guys,
I switched to the new 1.3 release and it seems that the Java backend
isn't able to parse the rpc json-string of the frontend anymore.
This happens when I try to send a Javascript date object.
Here is the stack trace:
java.text.ParseException: Expected a ',' or '}' at character 127 of
{"service":"communicator.Former","method":"updateForm","id":10,"params":
[[{"data":[{"cell":"fromDate","oldValue":2010-12-07T23:00:00.000Z,...}
at org.json.JSONTokener.syntaxError(JSONTokener.java:525)
at org.json.JSONObject.<init>(JSONObject.java:228)
...
The first ':' in "2010-12-07T23:00:00.000Z" produces the problem.
It looks like the long-discussed deprecation of our custom Date object
formatting has begun. Date formatting is now using qx.util.Json which has our
custom Date manipulation defaulting to disabled. It looks like you can enable
it by setting the static variable qx.util.Json.CONVERT_DATES = true. You can do
that a single time at application startup.
Derrell
Hi Derrell,
it's not only a problem of the custom Date manipulation in the past, the json
string is invalid.
The (new) string representation of the date should be enclosed in double quotes
(").
How I handle to create a Java date object in the backend with this new format
is another problem ;)
For now, I'll try the workaround you mentioned.
Regards,
Andreas
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
