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.
