What I'd like to do is the following. Basically, I want to keep the two different database(table) to be the same. One db table is the sender(source) and the other is the reciver table(target). I want to make sure that data integirty is managed well. ( No lost data and duplicates between the source and the target table)
Could this scenario be done by Servicemix ? How do I configure the service flow using the standard jbi components ? First I was thinking a poller component which sends data from the source table periodically and I had to put a jms queue between the source and the target table where the data is kept for during the transaction. In the sender table, I added a column(flag) for checking wheather the data(table row) has been sent by sender table or not. I wanted to have two different transactions for sender and receiver. If the jms queue crashed in the middle of transaction, then the sender shouldn't mark the flag column which meaning the data has been sent. How do I make sure that the poller can not initiate another transaction if the previous transaction(sending transaction) hasn't been done ? How do I configure the sender service flow using the service components(jms,jdbc,...with xa ?)? Or do I need to implement a pojo class where it does all the sending part ? For the receiving part, it looks like ok to compose the service flow. (Since jms comp. can initiate the xa transaction with jca flow) Thanks a lot. -- View this message in context: http://www.nabble.com/Could-service-flow%28vs.-customized-component%29-can-cover-most-of-the-requirements---tf3937776s12049.html#a11168436 Sent from the ServiceMix - User mailing list archive at Nabble.com.
