camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Ertl <>
Subject Custom component for weird legacy format
Date Thu, 23 May 2013 13:56:47 GMT
Hi everybody,

we have to implement a route that listens on a defined http-port and
receives a message with a very strange legacy format. Partly XML, partly TLV
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 call convertToType after receiving the message
via the jetty-component?
What would you propose?


View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message