I'm not sure how useful this tip is, but I think this might be a good one. I would take the exam objectives, and the spec, and start writing exam questions yourself. I think the very process of doing that would cause you to read and understand the pertinent parts of the spec, and you never know - you might come up with a pretty good mock test I'm not sure you could do this without some additional information/experience, but I think it might be a reasonable way to study. The objectives are *that* clear (in most parts, anyway, right Kathy? ) Just a thought!
I think this is a fabulous idea!! And if everybody starts posting questions here, we can get somewhere fast. Do NOT worry if the questions are not "good" or well-written, or even completely accurate. Just give it a try, and we'll help shape and correct the questions you post. That will be one of the best things -- if not THE best -- that we can do here, in the short term. My other advice: make flashcards. Take 3 x 5 notecards, and write questions to yourself on one side (not mock-exam questions, more like fill-in-the-blank questions) and the answer on another. Take them EVERYWHERE with you from now until the exam. Read them at traffic signals, on the train, at the cafe, waiting for The Matrix Reloaded to start (using the light of your cellphone to read by ) or whatever. I would not have passed SCJP my first time without them. Just go through the objectives, like: "Which three types of methods are you required to implement in a Session Bean?" Answer: 1) Methods of the SessionBean interface (which your bean must implement) 2) Business methods from your COMPONENT INTERFACE. (all business methods defined in your component interface must be implemented. Otherwise, the poor client will call x.doReallyImportantStuff() and when the container gets the call, it (the container) will completely freak out because your bean class can't do it!) (yes, most deploytools will stop you from getting that far, but there's no guarantee...) 3) ejbCreate methods from your HOME INTERFACE (a matching ejbCreate for every create in your home) ========================== Or... "What does ejbPassivate mean to a SessionBean and to an EntityBean?" Answer: "For a SessionBean, it means the bean MUST be stateful, and is about to be... passivated, which means taken out of RAM to preserve resources while we wait for the client to make up his mind and add something else to the shopping cart... at which time the container will say, "Whoa! Somebody's calling a business method again; I better get this bean re-activated. Remember: stateless beans are NOT passivated. They just go back to the pool, so they are not consuming any resources on behalf of a client EXCEPT when the client is in the middle of a business method invocation on the bean." "For an EntityBean, it means the bean is going to be put back into the pool, losing his identity as a particular entity. In other words, his 'state' will be *erased* as he slides back to the pool without a care in the world... and no primary key... ready to sip umbrella drinks and cavort with the other beans in the deep end until the container realizes that , 'Hey, somebody is trying to access Gus T. with a primary key of 42, so we better pull a bean out so that it can *become* Gus T.' at which time, the bean will be reactivated." OK, that's actually way more than I would put on a flashcard, but I've just had an illegal dose of caffeine and I got carried away cheers, Kathy p.s. great advice Kimberly!