Originally posted by Nicholas Cheung:
I think the answer is A.
Obviously, B is incorrect because the Entity Bean does not contain a create() method, since this is defined in the home interface, and when it is implemented in the bean, the ejb prefix will be added.
D is incorrect because the DB is complaining about the primary key violation. It will be correct, if the error is solely about saving the bean data, without any key issues.
In fact, choice A and C are quite similar, however, ejbPostCreate() is used to finish any actions that cannot be performed in ejbCreate() as the bean is not completely created at that moment. However, upon ejbCreate() is completed, the bean is created and the data is appear in the DB. Thus, if a data item cannot be inserted into the DB due to PK violation, problems should be appeared in ejbCreate().
Does this make sense?
Nick
Originally posted by Nicholas Cheung:
Hi Howard,
I saw Thomas has made a request to the publisher to send me your book on March 1.
Meanwhile, I have read the TOC of your book, and the preface.
However, I would like to know, could you provide us a objective mapping of IBM 287 with the chapters of your book?
I think this can help us to prepare well in a short period.![]()
I will take the test on 21 March, but I will first take 486 on 14 March.
Thanks a lot.
Nick.
Originally posted by Jim Yingst:
Luap Samoht would be a cool name though.
Originally posted by Adrian Yan:
I don't like to extend RuntimeException unless I can't figure out anything better.
Originally posted by Jorge Blaz:
Hi,
I've experience with Java, Servlets, Jsps and also some knowlegde of Struts.
Now i have some free time and I wanted to learn a new tecnology that could be very helpful for a job in the future. I have no idea of EJBs nor Web Services. Which tecnology do you think it's more useful now in J2EE projects?. Or are both very important as I guess?
Thanks in advance
Jorge