On 2/27/07, tom.b <[EMAIL PROTECTED]> wrote:
I'm not quite sure what is the most appropriate place to implement a custom
service:
a) in an external service that is invoked by a Binding Component, or
b) in an Service Engine, residing in the JBI environment.
Suppose I would like to implement a new piece of business logic, that always
provides the message "hello world" to the service consumer :) Where can I
best implement this business logic?
The JBI documentation tells me that an SE is supposed to implement business
logic, so it seems an obvious place to me.
I can understand that any existing business logic, e.g. my existing
HelloWorld(TM) server implemented in COBOL would have to be addressed as an
external service, but I'm wondering what the considerations could be, for
newly developed business logic in Java.
If it's a new service that is only going to be deployed on the
Normalized Message Router (NMR) inside the JBI container, then it
should be implemented as a JBI service engine. If it needs to speak to
services external to the NMR via a remoting protocol (e.g., HTTP, FTP,
SMTP, etc.) or vice versa, this will need to take place via JBI
binding components.
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/
