On Sat, Jun 25, 2016 at 5:23 PM, ssatguru <ssatg...@gmail.com> wrote:
> camel salesforce component has issues with dates less than or equal to
> "November 18th 1883".
>
I am intrigued to hear what is the use-case is for using dates going
so far back?
And if there is such a problem, has it been reported to jodatime ?
Maybe there is a fix already in a newer version?
> These dates are serialized to a format unacceptable to SalesForce.
>
> For example
>
> Date 1800-01-01 is serialized by this component as
>
> 1800-01-01T00:00:00.000-05:50:36
>
> Salesforce responds with the following error
>
> {message:'{errors:[{"errorCode":"JSON_PARSER_ERROR","message":"Cannot
> deserialize instance of date from VALUE_STRING value
> 1800-01-01T00:00:00.000-05:50:36 ...
>
> The problem has to do with the seconds in the time zone part (:36 in above
> example)
>
> The issue arises because camel salesforce component use the Joda DataTime
> library which handles date before "November 18th 1883" in this manner
>
> see here for some discussion on this
>
> https://www.kevinhooke.com/2010/07/23/whats-the-significance-of-nov-18th-1883-to-software-development-in-the-us/
> <https://www.kevinhooke.com/2010/07/23/whats-the-significance-of-nov-18th-1883-to-software-development-in-the-us/>
>
> or
>
> http://stackoverflow.com/questions/14282423/why-when-year-is-less-than-1884-it-remove-few-milliseconds
> <http://stackoverflow.com/questions/14282423/why-when-year-is-less-than-1884-it-remove-few-milliseconds>
>
> Maybe the salesforce component should convert the date or date time to
> milliseconds format rather than the zoned format. Salesforce seems to
> accept this format
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-salesforce-component-date-time-issue-tp5784399.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
