ServiceMix message transformation question

[Paul Ryan Kuykendall <pk...@gmail.com>]

Hi,

I am new to ServiceMix and have some questions about what sort of development effort will be required to do something.  We are considering using ServiceMix as an "application" service bus to integrate a new product line with a collection of existing legacy services.

The legacy services utilize a custom binary protocol (packed little-endian C structures).  I want to wrap these legacy services with a RESTful interface and isolate the protocol payload from our existing routing structures.  Example:

MessageRoutingControl
ControlParameters
RequestParameters
RequestData

We only want to expose the various "RequestData" portions as the service and the "RequestParameters" as some sort of header information.

I've created a custom Netty protocol encoder and decoder that is able to read and write the entire message structure.  What I'm not so sure about is what other components will be required to enable ServiceMix and Camel to properly route and transform the messages from a (yet to be defined) format into something that can be passed over the wire.

Thank you for any help.

/Paul