Hi
We did a prototype with such a scenario and it is not that simple and
it is also quite a hack to make it work:
- Created a SU using ServiceMix-Bean and having for each DB /
Application its own service
- You can extend a base class in each service to share code
- Make sure that ServiceMix has a Transaction Manager
- Make sure that you use "ST" (straight) flow and enable it in the
ServiceMix configuration
- Send the message with "sendSynch()" to make sure it is sent in the
same thread
- The JDBC service must be able to pick up the Tx Manager from
ServiceMix and set it on your Data Source or use a transactional
resource that can deal with it
Hope that helps
Andreas Schaefer
CEO of Madplanet.com Inc.
[EMAIL PROTECTED]
On Sep 12, 2007, at 11:57 AM, cjn wrote:
Hi,
Can anyone point me to some good examples of composing
transactional (i.e.
JDBC) services with ServiceMix? All I can find is messaging-based?
Or is
there a way I can re-structure my application to be messaging based?
I'd like to compose some new transactional services by re-use some
existing services, mixed with some new logic. For example, imagine
some
existing functionality that must definately be transactional, like
financial
functionality. Each application that will use this service will
also have
it's own logic. Essentially I'd like to compose a series of new
services:
app 1 + re-used logic
app 2 + re-used logic
app 3 + re-used logic
each of which needs to be transactional (e.g. if app1 or re-used
logic fails
then both roll back).
Is there a way of doing this with JDBC transactions in ServiceMix,
or is
there a way to convert this kind of structure to be messaging-
based? Please
excuse my complete ignorance on message-oriented architectures!
Thanks,
Chris.
--
View this message in context: http://www.nabble.com/Service-re-use-
and-Transactionality-tf4431418s12049.html#a12642059
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Andreas Schaefer
CEO of Madplanet.com Inc.
[EMAIL PROTECTED]
