[
https://issues.apache.org/jira/browse/CAMEL-12334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400585#comment-16400585
]
ASF GitHub Bot commented on CAMEL-12334:
----------------------------------------
zregvart commented on issue #2254: CAMEL-12334: Mapped date to LocalDate and
time to LocalTime
URL: https://github.com/apache/camel/pull/2254#issuecomment-373421599
I think the most widely used one is ZonedDateTime for holding date and time
values. That doesn't prevent us from supporting all combinations and letting
the user choose the type in the data transfer object.
The default, I think, in the Maven plugin for generating data transfer
objects should stay ZonedDateTime. We could make it configurable, so that the
user can some control over the code generation. That would also be good in the
interest of keeping the generated code backward compatible.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Salesforce DTO does not use correct datatype for "date" and "time" field
> ------------------------------------------------------------------------
>
> Key: CAMEL-12334
> URL: https://issues.apache.org/jira/browse/CAMEL-12334
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Affects Versions: 2.20.2
> Reporter: Hemang Ajmera
> Priority: Major
> Labels: maven
>
> The DTO classes generated by the Maven plugin uses ZonedDateTime for all three
> * datetime
> * date
> * time
> The generation works fine, but is is not able to marshal/unmarshal correctly.
> The DTO should use different kind of field. My suggestion is to use
> * ZonedDateTime for datetime
> * LocalDate for date
> * LocalTime for time
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
