Bug? Date off by a Month

[atomatom]

Using a BasicDatasource and a nightly build of Pro from 2 days ago.

On the server I have a date which is 2011-06-02. It is this value all through the server code. By the time the SmartClient console picks it up, it is off by a month and is 2011-07-02.

Changing the DS.xml to specify the type as "datetime" serializes the date correctly.

{
    "operationId":"custom", 
    "transactionNum":13, 
    "httpResponseCode":200, 
    "transport":"xmlHttpRequest", 
    "status":0, 
    "httpHeaders":{
        "Content-Type":"text/plain; charset=utf-8", 
        "Cache-Control":"no-cache", 
        "Pragma":"no-cache", 
        "Expires":"Tue, 31 May 2011 19:09:24 GMT", 
        "Transfer-Encoding":"chunked", 
        "Server":"Jetty(6.1.x)"
    }, 
    "isStructured":true, 
    "results":{
        "endRow":1, 
        "queueStatus":0, 
        "totalRows":1, 
        "isDSResponse":true, 
        "invalidateCache":false, 
        "status":0, 
        "startRow":0, 
        "data":[
            {
                "date":"2011-07-02", 
            }
        ]
    }, 
    "isDSResponse":true, 
    "invalidateCache":false, 
    "data":[
        {
            "date":"2011-07-02", 
        }
    ], 
    "startRow":0, 
    "endRow":1, 
    "totalRows":1
}

[Isomorphic]

This was a recent regression, just fixed today. It crops up if the current calendar day for your machine happens to be 30 or 31 (which doesn't exist in every month).