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.
Hi all, I just completed reading the book HFEJB. I am planning to read some parts of the EJB specs before taking the exam in few weeks. Could anyone suggest few chapters in the specs that ARE to be read before taking the exam ? I understand that ideally I should read all the chapters before the exam; but because I have completed HFEJB, I want to read only the chapters in EJB specs that discuss topics that are not well handled in HFEJB. Some of you might have taken the exam and you might have thought that HFEJB could have done a better job in few topics. I will be glad if you can post the details on "must read" chapters from EJB specs.
I won't be able to tell you wich chapters you definately MUST read because I haven't read them all. What I did was studying the HF book, and look up the details in the spec whenever something was not entirely clear to me. I made mock exams on ejbcertificate.com and the HF book, and when I missed one, I went to the specs to read that part. Learned a lot by doing this.
Some thing I remember looking for in the specs: * allowed TX attributes, for MDB's, statful SB's using SessionSynchronization, ... * Exceptions thrown on methods as remove(Object pk) and remove(Handle h) when not allowed * NoSuchObjectException or RemoteException to the client, and things like that * I tried to read a lot about the roles (Bean provider, Application assembler, ...) and their responsibilities. HF didn't make a clear difference between the Deployer and the System Administrator in my humble opinion. * <exclude-list> tag in the ejb-jar (details not in HF)
One final tip: make sure you know and understand all 'Bean Things' (HF)allowed/not allowed for all container callbacks ! (look for the cheat sheets on javaranch)
Good luck !!
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