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 (tag-length-value). 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?
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.
