This week's book giveaway is in the Testing forum.
We're giving away four copies of Data Structures the Fun Way: An Amusing Adventure with Coffee-Filled Examples and have Jeremy Kubica on-line!
See this thread for details.

Krishna Thotakura

+ Follow
since Feb 12, 2004
Merit badge: grant badges
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Krishna Thotakura

I just passed the SCBCD exam with 88%.
Thanks Kathy and Bert for coming up with HeadFirst EJB. I generally avoid tech books with humour. But HF-EJB was really great - Tons of humour and creativity along with the EJB material.
I read HF-EJB twice. Then referred to some sections of the EJB Spec. I also read parts of Mastering EJB.
I did the practise exams on and I think the tests provided me with a great deal of revision. But dont be disappointed if you dont score well on the tests at I didnt do well in them either.
My HF-EJB final exam score was very close to the actual score.
Valentin Crettaz's cheatsheets on deployment descriptor and Objectives-Spec mapping were awesome.
Thanks to Reid and all the forum participants.
18 years ago
Here is a question from
"Which of the following statements are requirements for a session bean's session bean class? [Check all correct answers]"
"The class may implement the session bean's component interface" has been marked as correct answer.
I cant agree with that.
(w.r.t HF-EJB pg85) Bean class should not be able to implement (remote) component interface directly because remote component interface extends EJBObject, and hence implements java.rmi.Remote interface.
I know you can do a simple OOD trick to get around that problem.
Do you see these kind of questions on the actual SCBCD exam ?
I have also seen some mock exams using the word "session object" while they were actually referring to "ejb object" that is tied to the bean instance. Is "session object" a common way of referring to "ejbobject" tied to bean instance?
I looked at page 233 of the EJB 2.0 final release spec. And the query that you showed was given as an example of INVALID EJBQL query.
Hi Reid,
I really appreciate your quick response.
Regarding CASE A that you described - "is it possible for the session bean to receive a RemoteException if the remote bean's container performs a transaction rollback?".
I think the answer is a definite Yes.
If the question was worded "will the session bean client receive a RemoteException if the remote bean's container performs a transaction rollback?".
Then my answer would be "No (not always)".
I was reading the portion of the Spec you pointed out. And i have another question with reference to Table 15, first row on page 376 :
B1.m1() has tx1.
It calls B2.m2() that has RequiresNew trans-attribute. Let us call this transaction tx2.
Now, if B2.m2() throws a system exception or error,
Then container will discard B2 and mark tx2 for rollback - right ? B1 will get a RemoteException or EJBException.
The spec says "If the client executes in a transaction, the client's transaction may or may not be marked for rollback" What does this mean ?
Under what circumstances will transaction tx1 be marked (by container) for rollback ?
If B1.m1() does not attempt to catch RemoteException/EJBException and let the system exception propogate through, then will tx1 be marked for rollback by the container ? Is that what the spec is talking about ?
Here is a question from
Which of the following statements are true when a session bean's client receives a java.rmi.RemoteException? [Check all correct answers]

1. The container does not throw the java.rmi.RemoteException if the container performs a transaction rollback.
1 is marked correct.
I do not understand why. if the business method of a remote session bean throws a system exception, wont the container rollback the transaction and throw a RemoteException for the client ???
what do you think about the quality of questions on ?
I think you are right. You cannot access resource managers in the ejbCreate() and ejbRemove() methods. If i understand correctly, it is because these methods do not run in any transaction. And methods that do not run in a transaction cannot access resource managers or other enterprise beans.
Anyone, please correct me if i am wrong.