Your comment is a perfect example of why companies should be very careful when they consider outsourcing work to another country. The communication breakdown can be costly.

You bring up a good point about the wide spread industry standard must have skill sets under the large Java umbrella.  Generally when I interview people, I'm bringing them in longer term.  This makes it easier to overlook missing frameworks, exposure to niche tools, etc.  I generally want a candidate with relevant experience.  If you have worked on Struts, you can probably make the transition to Spring MVC.  If you have used pico container, you can probably make the shift to Spring.  If you know JDBC and understand that high level concept of what an ORM framework is, Hibernate will not be a huge undertaking.  The biggest turn off to me is when people can't justify their resume.  If you put something on your resume and you aren't prepared to speak to it, then you don't get the job.  It's that simple.  An interview is a two way street too.  If I showed up to the interview and couldn't explain what my group did or what technologies we used, I would expect the candidate would have the same opinion.