.465427.n5.nabble.com/Custom-component-for-weird-legacy-format-tp5733030.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
Am Do, 23. Mai 2013, um 15:56, schrieb Frank Ertl:
> just to write a new TypeConverter and call convertToType after receiving the
> message via the jetty-component?
This should not be too difficult. Parsing the Exchange body sounds like
the difficult part, not receiving it via HTTP. You could
the
> message
> via the jetty-component?
> What would you propose?
>
> Regards,
> Frank
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Custom-component-for-weird-legacy-format-tp5733030.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
; > I wonder what would be the best option to overcome this mess. Writing a
> > custom component that could work as a consumer endpoint (somehow using
> > jetty, maybe by extending the jetty-component) or would it be better just
> > to
> > write a new TypeConverter and
Hi all,
many thanks for your helpful responses. As I don't have to deal with headers
I'll write a custom DataFormat.
Regards,
Frank
--
View this message in context:
http://camel.465427.n5.nabble.com/Custom-component-for-weird-legacy-format-tp5733030p5733070.html
Sent from the Cam
