[
https://issues.apache.org/jira/browse/CAMEL-9105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733783#comment-14733783
]
metatech commented on CAMEL-9105:
---------------------------------
Thanks [~sergey_beryozkin]. Regarding the priority of the fix, it is not really
urgent, because there is a (temporary) workaround : it is possible to redefine
the "toString" method on the Date object in the application code to write the
date in the format previously used.
> Camel DefaultHttpBinding should convert response Date headers to
> HTTP-friendly format
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-9105
> URL: https://issues.apache.org/jira/browse/CAMEL-9105
> Project: Camel
> Issue Type: Improvement
> Components: camel-http-common
> Reporter: Sergey Beryozkin
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.16.0
>
> Attachments: camel9105.txt
>
>
> This is related to CAMEL-9091 except that the optional transformation of Date
> and also Locale instances can be of use to all of Camel HTTP consumers
> depending on a Camel transport. It is also likely a cleaner solution because
> at the CXF component level the headers may be going out to JMS/etc flows
> Note the use of type converters will still be possible, however installing a
> global type converter converting Date to HTTP-friendly rep is deemed
> sensitive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
