Davide, There isn't a fixed answer to that question, you could write your database persistent steps as a Service Engine, however but nature the service engine tends to be a service that can be deployed more than once with a different configuration.
If you want to implement business logic and persistence you might want to look at the JSR-181 Service Engine, since this allows you to write simple POJO's to do the work you want without worrying about JBI message exchanges. P On 7/7/06, haranbanjo <[EMAIL PROTECTED]> wrote:
Bruce :-D Another question (if you have time for answer me). Service engine is a JBI component that perform some business logic. The documentation says... "data transformation, sophisticated routing, message coordination facilites". So, this "business logic" is referred exclusively to manage messages ... or is "permitted" to have my personal business logic in it? For example... i need to write some data on a Database as response of a message. Which is the best choise: 1) insert the code (connection / query execution) in my service engine. So when my service is called the data are written to the database. 2) The ESB is only for routing messages. So i must create a remote service (so not in the ESB) that perform the serialization on the database. In this way i must create 2 service engine. The first receive the message (ex "insert this new data in the database").... then this message is routed to the 2 service over NMR, and subsequently transported to my remote service that write data to the database. Thanks Davide -- View this message in context: http://www.nabble.com/ServiceMix-Beginner---Help-me-%3A-D-tf1899815.html#a5215159 Sent from the ServiceMix - User forum at Nabble.com.
