This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by Javix Protocol: Can anyone here brief me in detail about the ACID properties that support Transaction in EJB.
Not sure about the phrasing there: EJBs support Transactions which should support the ACID properties, not the other way around. The EJB 1.1 spec states that EJBs support distributed transactions (flat rather than nested), and as such they provide facilities for making completion of a unit of work atomic, and isolate the units of work from one another. I would think that consistency checking is delegated to the JDBC driver and database itself (although it depends upon the EJB type and methods used for database mapping). Facilities for durability are also provided, but I think much depends upon the JDBC driver. The servers that manage the EJB containers that I have come across use JDBC for their database connectivity. I recommend that you read the EJB 1.1 specification, especially chapter 11, which goes into more detail about the EJB and its transactional capabilities. I'm not sure what changes in transactions are brought in with the EJB 2.0 spec (not at Final Release stage yet).
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com