Hi, I am facing a problem in handling transaction suport in geronimo 1.1.1
The situation is like this: I have one Message Driven Bean deployed on geronimo 1.1.1.The MDB, on receiving the message will do a Database updation.After the databse updation is done, the next thing that would be done by the MDB is calling one more different functionality.If this functioanlity fails, then the database updation done in the earlier step, would roll back, the rows updated, would roll back. I am very new to transaction support in geronimo.I am not sure whether this kind of functionality would be possible or not.Whthere geronimo 1.1.1 has transaction support or not..and how to implement that support in this particular use case. Please help me and let me know what would be the best way to achieve this. Regards, Anshuk **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***
