William, The promo doesn't officially start until tomorrow. I can answer this question though, so you don't have to wait for the authors!
O/R mapping: Tons. Most of the entity bean content describes O/R mapping. There is also a chapter dedicated to O/R mapping issues.
MDBs: There is one chapter dedicated to MDBs. There are also comments about MDBs in different places throughout the book where it applies. For example, the design and transactions sections include information on MDBs.
We have a full chapter on MDB and more than half of our contents cover JPA. Here is the TOC for the book.
1. What's what in EJB 2. A First taste of EJB 3. Building Business Logic with Session beans 4. Messaging and Developing Message Driven Beans 5. Learning Advanced EJB Concepts 6. Transactions and Security 7. Implementing Domain Models 8. Object-Relationship Mapping 9. Manipulating entities with EntityManager API 10. Using the Query API and the Java Persistence Query Language 11. Packaging EJB 3 Applications 12. Effectively Integrating EJB 3 across Your Application Tiers 13. Taming Wild EJBs - Performance and Scalability 14. Migrating to EJB 3 15. Exposing EJBs as Web Services 16. EJB 3 and Spring
Appendix A. RMI and JNDI Appendix B. Reviewing relational databases Appendix C. Annotations reference Appendix D. Deployment descriptors reference Appendix E. Installing and configuring the Java EE 5 SDK
I see from previous reply that your book contains a lot of apendices (including annotation reference). It is a good idea. According my knowledge I think one of very good features in EJB 3.0 is using of extended persistence context and interceptors. I am very glad about this improvement. My question are :
1. Do you subscribe mentioned topics in more details ?
2. Is already possible to create custom annotation with interceptor functionality ?
3. Is already possible to have REQUIRED attribute for let's say just one "finalization" method like bookSeats() in the case of STATELESS session bean ? (other methods before this final would be run without transaction context - transactional attribute for a bean is NOT_SUPPORTED and because of that all transaction would be queued and processed just in the final method). As well as I know there were some talks about this in EJB 3.0 Expert Group. So far it is possible only for STATEFUL session beans and I completely agree with that. I do not think it is good idea to put it into stateless session bean.
SUN Certified Enterprise Architect SUN Certified Business Component Developer SUN Certified Developer For Java Web Services SUN Certified Programmer SUN Certified Web Component Developer SUN Certified Mobile Application Developer
God is a comedian playing for an audience that is afraid to laugh - Voltair. tiny ad: