Hi Maybe it sounds like a better idea to use a iso-xxx date to be consistent, instead of a toString that may be OS locale dependent etc.
Or it could store the value as a long value of the epoc. On Mon, Feb 12, 2018 at 12:19 PM, Quinn Stevenson <qu...@pronoia-solutions.com> wrote: > Sorry - ignore that. That feature is used to customize the mapping of the > key names - not the values. > > The only way I can think of right off hand is to add you’re own bean that > manipulates the header values before you send them. > > >> On Feb 12, 2018, at 10:14 AM, Quinn Stevenson <qu...@pronoia-solutions.com> >> wrote: >> >> You can provide your own implementation using the jmsKeyFormatStrategy URI >> Option. >> >> >> >>> On Feb 12, 2018, at 8:34 AM, Probert, Matt <matt.prob...@metoffice.gov.uk> >>> wrote: >>> >>> When messages are produced to ActiveMQ, Camel JmsBinding converts >>> java.util.Date message headers to string via Date.toString(). >>> >>> I want to override the conversion, to give IS0 8601 strings. >>> >>> Is there a way to inject a custom JmsBinding to do it? Or some other >>> standard way? I don't want to modify existing route definitions, if >>> possible. >>> >>> I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. >>> Routes are defined in the spring XML DSL. >>> Cheers, >>> Matt >> > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2