> That's a serious bug. Please add it to bugzilla.
Done: http://bugzilla.qooxdoo.org/show_bug.cgi?id=4502
By the way, the workaround you mentioned (qx.util.Json.CONVERT_DATES = true)
works, to get the good old "qooxdoo-date-convertion" ;)
Thank you very much.
Regards,
Andreas
On Thu, Dec 16, 2010 at 09:00, Fink, Andreas wrote:
> 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 (").
>
That's a serious bug. Please add it to bugzilla.
>
On Thu, Dec 16, 2010 at 07:54, Fink, Andreas 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.ParseEx
On Thu, Dec 16, 2010 at 07:54, Fink, Andreas 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:
>
> j
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
{"
