Some confuse about the Binding Compoent

[Jackey Ding <No...@gmail.com>]

Is BC just a delegation of the service outside of the servicemix running
time? And the real service must be publish as a webservice that servicemix
can access?

-- 
View this message in context: http://www.nabble.com/Some-confuse-about-the-Binding-Compoent-tp16269262s12049p16269262.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Some confuse about the Binding Compoent

[Lars Heinemann <la...@compart.net>]

Jackey,

a BC (binding component) is just a connector from and to another
protocol. It will normalize messages coming from outside the bus so that
everyone inside the bus can interprete them and it will de-normalize messages from inside the bus to outside the bus so that another service outside the bus may understand them. A good example is the file system. You need the servicemix-file binding component to translate a file found in file system into a normalized message that will be sent to the bus. In this case the contents of the file will be put to the message body and some specific headers are created. (if binary marshaler is set, then the file is copied to the message attachments instead)

A binding component should always work as generic as possible, so no business logic and no specific things...just do a plain conversion.

A service inside the bus will only interprete and understand normalized messages. So these binding components are a must have if you want to communicate with the world outside the bus.

If you got further questions just let us know.

Regards,
Lars





Jackey Ding schrieb:
> Is BC just a delegation of the service outside of the servicemix running
> time? And the real service must be publish as a webservice that servicemix
> can access?
>
>