Hello Friends, I am having a problem in the form of a EJB pattern which suggests using aggregated classes instaed of making all tables as beans. I have a Session Bean talking to a CMP Entity Bean. The Entity Bean is having aggregated classes. The aggregated classes do not access the database for every business method of the bean. Instead the aggregated classes access the database only when the ejbload() and ejbStore() of the Entity Bean is called. The CMP bean has an aggregate class (corresponding to one table) which is populated when ejbload() of Entity Bean is called. Similarly the aggregate class is written to the database when the ejbStore() of Entity Bean is called. These are achieved by means of JDBC calls to the database present in appropriate methods of the aggregate class. These appropraite methods are called depending on ejbLoad() or ejbStore() of Entity Bean. Now i am having the problem in the form of Transaction Mgmt. How do i do transaction mgmt. for the aggregated class. My Session bean is always starting a new transaction for its business methods. Also the entity bean requires transactions for its busines methods. But when the Sesion throws an exception the database update performed by the aggregated class should also be roled back. Can u pl. suggest how i can achieve this. I have tried using Transactional and Non transactional DataSource for connecting from aggreagted class but to no avail. Can anyone suggest me something? Regards, Prateek. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
