I just obtained my
Sun Certified Web Component Developer certification. Even though it’s too much little nitpicky details for my liking, getting the overall picture is quite useful, and now and then it saves quite a lot of time fixing an issue. Especially fixing someone else’s messy issue
Studying the Servlet specification feels a bit like learning Perl, of which the main man page defines There’s more than one way to do it. Divining how many more is left as an exercise to the reader. The new servlet specification seems to only extend on the already existing methods, generating many ways to accomplish the same thing (like the language Perl). Next time, they’d get rid of ‘old tag’ support, tld-files, and inconsistent naming. They could end up with a common sensible spec, and supply an additional backwards-compatibility extension (e.g. some special jar) for people running old stuff. Otherwise you’d end up with creators claiming that It’s ugly but useful
.
I prepared for the exam mostly by studying Head First Java Servlets and JSP -all study books should be written like that-, playing around with Eclipse and Tomcat, and reading the JavaRanch tips on the exam. A few things are a little wrong in the book; like the non-mandatory jsp:root element for jsp-documents. Additionally, I should have read about dynamic attributes because it’s not in the book, but you’re required to know for the exam (as I found out). Better luck next time