This is a side rant -- so feel free to ignore. I don't understand why recruiters bother to target EJB or Web Services for candidates.
I have done both. And in both cases, I spend a small percentage of time, setting the home, interface, WSDL, etc. and then spent the majority of the time coding the actual service. This majority of code would have been the same regardless of whether part of an EJB or web service.
I understand why it is important to target
servlets or JSPs -- as there is a tighter integration with the web server. But for EJBs and web services, I would rather hire based on knowledge of the subject matter, and get the new hire a book.
Henry