Java Transaction Design Strategies
Paperback, 116 pages
| Price: | $24.97 |
|---|
Ships in 3–5 business days
Understanding how transaction management works in Java and developing an effective transaction design strategy can help to avoid data integrity problems in your applications and databases and ease the pain of inevitable system failures.
This book is about how to design an effective transaction management strategy using the transaction models provided by Java-based frameworks such as EJB and Spring. Techniques, best practices, and pitfalls with each transaction model will be described. In addition, transaction design patterns will bring all these concepts and techniques together and describe how to use these models to effectively manage transactions within your EJB or Spring-based Java applications.
The book covers:
- The local transaction model
- The programmatic transaction model
- The declarative transaction model
- XA Transaction Processing
- Transaction Design Patterns
Ratings & Reviews
Log In to review this item
Review Java Transaction Design Strategies
Lulu Sales Rank: 1217
9 People Reviewed This Item
I am writing this review to counterbalance the previous review, which is absurd. Java Transaction Design Strategies explains how to use transactions in Java and J2EE, with specific recommendations based on extensive real-world experience. See for yourself. Or, trust the irrelevant grammar advice from the previous reviewer, who believes in a discipline called discreet [sic] mathematics.
buy degree | Corllins University
buy degree | Corllins University
Great book for Java EE transaction! I could not find such good book on this area. It give me great help on my EJB 3 project. I should get this book earlier.
"Lacks effective writing"
This book has the typical trademarks of technical manuals that are laced with technical details yet lack effective writing. Mr. Richards' grammar and sentence structure make the reader wonder what he/she has just read. This usually results in re-reading sentences or even full paragraphs. I have some suggestions for Mr. Richards’ to improve his writing skills. When beginning a new paragraph, Mr. Richards needs to pay more attention to placing the main idea in the first sentence. Also, reduce the use of excessive subordination and run on sentences. Eliminate the word "there" where the use of a noun will make sentences clearer. For example: "Fortunately, there is... More >
This book has the typical trademarks of technical manuals that are laced with technical details yet lack effective writing. Mr. Richards' grammar and sentence structure make the reader wonder what he/she has just read. This usually results in re-reading sentences or even full paragraphs. I have some suggestions for Mr. Richards’ to improve his writing skills. When beginning a new paragraph, Mr. Richards needs to pay more attention to placing the main idea in the first sentence. Also, reduce the use of excessive subordination and run on sentences. Eliminate the word "there" where the use of a noun will make sentences clearer. For example: "Fortunately, there is... More >
"Great book on the transaction subject"
the best material on this subject I have ever read, clear and concise
"Where's the UML?"
Although there are some very noticeable grammatical and sentence structure issues in the first few pages, for the most part, these issues are resolved around page 11.
In my brief scan of the book, I saw classes and methods mentioned in paragraphs. And when I saw the diagrams it was clear what class owned what responsibilities. However, when the author mentions the need to call certain methods based on certain conditions, I expected to see some UML. I saw instances where class diagrams, activity diagrams and sequence diagrams could have been extremely useful … and simple to put together. When I read the back of the book and saw Mr. Richards' credentials, I was... More >
Although there are some very noticeable grammatical and sentence structure issues in the first few pages, for the most part, these issues are resolved around page 11.
In my brief scan of the book, I saw classes and methods mentioned in paragraphs. And when I saw the diagrams it was clear what class owned what responsibilities. However, when the author mentions the need to call certain methods based on certain conditions, I expected to see some UML. I saw instances where class diagrams, activity diagrams and sequence diagrams could have been extremely useful … and simple to put together. When I read the back of the book and saw Mr. Richards' credentials, I was... More >
You Recently Viewed
![[Loading...]](http://static.lulu.com/images/ajax-loader.gif?20120131141155)
