On 3/12/07, Owen Thomas <[EMAIL PROTECTED]> wrote:
Hi Giullaume
Thanks to you and Bruce for the tip. I think that it would be great to
keep away from writing a component because I looked at what classes and
interfaces a BC had to extend and implement, and it aint pretty. Your
advice is welcome indeed.
What is the difference between a BC and SE? Is this difference manifest
in the API so that knowing which one to develop is obvious?
The differences between the two are certainly subtle. Below are
explanations of each one:
* Service engines (SEs) are engines that are deployed to the JBI
container and communicate only using normalized messages.
** Example: Consider deploying a BPEL engine to the JBI container -
this is deployed as a SE because it handles business process script
execution via the BPEL engine.
* Binding components (BCs) are bindings to services external to the
JBI container and use a remote protocol for communication with that
service.
** Example: Consider the servicemix-http BC which is used to
communicate with services external to the JBI container via the HTTP
protocol.
Does that help?
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
