I am preparing for SCBCD and following HFEJB. From the posts on this site I gather that one must read EJB 2.0 spec, which is about 500 pages. After reading HFEJB, most of the Specs will be repitition but it certainly provides additional information (which is very useful). Is there an alternative to reading Specs (like somebody's notes which has the same effect as reading Specs ... but not as long as Specs). Any help is appreciated.
Originally posted by Jaya Nettem: (like somebody's notes which has the same effect as reading Specs ... but not as long as Specs)
HFEJB is kind-of like that. View it as as a pre-digested exam-focused version of the specification. There is no need to read the specification end-to-end. HFEJB has references to the spec throughout which you should use to further your understanding of the topic. So if you are unsure about a mock question or you get it wrong go to the spec to clear up any misunderstandings.
Just keep in mind that if there is a contradiction between HFEJB and the spec - the specification is always right.
Invest some time in updating the information in your copy of HF EJB with the information found in the confirmed errata. If you find something else check the unconfirmed errata to see if somebody else already raised the issue.
You will want to print out some pages from the spec for that last cram session like:
and if you can, add the API description for each method - including which exceptions can be throw (and under what circumstances).
Also create a (one page) inheritance diagram of all the exceptions mentioned in HFEJB (and maybe a few more like java.lang.Throwable and java.io.IOException to complete the diagram) and mark them as Unchecked vs Checked and Application vs System (better yet organize them into clusters that make it easier to remember).
Finally create one massive (not necessarily valid) deployment descriptor with all the elements that you know you need to know and annotate the elements with you own comments and descriptions. [ October 17, 2005: Message edited by: Peer Reynders ]