Dear Ms. Sierra I am a Java Certified Programmer, and Before any thing I'd like thank you for your book on SCJP. My question: -I have no experience with EJBs and I want to get to practical stage ASAP. Has this book the practical approach or it only cover the exam's objectives? Still I appreciate your afforts on javaranch and your books, and wish u the best. Best Regards, Pourang Emami (email@example.com)
Howdy -- You have a good question... if you want to get to the *practical* stage, you really need THREE things -- a deep understanding and knowledge of what's really going on (how the Container is doing things), a good knowledge of best practices and patterns, and knowledge of the the specific J2EE server that you'll be using. We believe that we are the best at number one, even if you have no intention of taking the exam: deep understanding/knowledge of the topics (and in a way that you'll remember when you need to) We believe we can *help* with number two: best practices and patterns. We will be putting some of this on our web site within the next week, and there is *some* covered in the book. Mostly though, patterns and best practices are a result of knowing how things really work. If you truly understand how things work, most best practices are a result of applying that knowledge, combined with common sense and a good understanding of software/OO development in general. However, knowing some key J2EE patterns can help. We believe that both Ed Roman's book and the other O'Reilly EJB book do a good job -- probably better than ours -- at covering some of the more practical issues, although not in-depth. We do NOT help you at all with number three: vendor-specific knowledge of your Container. With that, you need both a book/manual that covers your specific server, AND hands-on experience to learn its quirks, problems, tricks, etc. For that, you might also find help on the non-cert EJB forum, or perhaps forums sponsored by the vendor of the Container you'll use. A LOT of issues related to EJB are indeed problems of the specific Container you're using, administering it, etc. At Sun, we always joked that it takes 15 minutes to write your code, and three hours to deploy and test it. Cheers, Kathy
posted 16 years ago
I just appreciate your complete answer. Actually I will use it all the way as a reference. You can even put it in the introduction section of your book. Thank you any way. Best Regards, Pourang Emami
Best Regards,<br />Pourang Emami
There are no more "hours", it's centi-days. They say it's better, but this tiny ad says it's stupid:
Devious Experiments for a Truly Passive Greenhouse!