Erm I failed .. 47% .. I went into the exam not reading a single spec or line in a book. I have however worked with webservices extensively mainly using apache axis. My main failing were basically around WSDL/UDDI/JAX.../SAAJ because I have yet to use these! The main problem I felt with the exam is that most of the nitty gritty stuff is normally abstracted out for you when dealing with webservices for example XML Schema is generated from your java classes so do you really need to know this! Oh well at least I got a sneak peek at the questions for when I really sit it.
The main problem I felt with the exam is that most of the nitty gritty stuff is normally abstracted out for you when dealing with webservices for example XML Schema is generated from your java classes so do you really need to know this!
This is a perfectly valid and understandable concern. Personally, I don't like working with a technology if I don't understand its underlying foundations and how the whole thing works and why it works the way it works... The fact that the available frameworks and tools abstract out the details does not mean you should not understand them. We can draw a parallel with pretty much any other technology. An EJB container does most of the transactional and persistency work on behalf of the EJBs, but this does not mean that the Bean Providers do not have to understand how transaction managers and databases work, or does it? If you are out there to solve problems using IT, it is always good to have some sound knowledge of what you are using, otherwise you might not be able to take important decisions at some point...