As I've mentioned before, we use the powerhouse three in the java world:
As I page through these resumes, I see quite a bit of struts, and that's it. Those with spring/hibernate experience are powerhouse architects (probably too expensive).
So if someone has WORK EXPERIENCE in spring and/or hibernate, they are getting an interview. Its that simple.
Blathering idiot? But you used spring at your last job? Come on in!
And for god sakes, don't make up design patterns then put them on your resume (or say that a core GoF pattern is a J2EE pattern)... if I interview you, I will embarass you in front of the other interviewers. What you put on your resume you should be able to talk with me about, in depth, and I will ask lots of questions ranging from what I expect a correct answer to architect type questions that have no right answers.
But, seriously, just having java experience for 20 years doesn't fly... someone with 3-5 years experience with those new techs will get you a great job with great pay (at least in this area). So for you aspiring Java developers (here's looking at you Sam), consider learning those techs when you feel ready for them... or consider switching to using them in your current job:
Struts is a front end web api, spring is a transaction/middle tier api, hibernate is an object/relational mapper (DAO/DB interaction). Hibernate is a stiff learning curve, but you can learn it very quickly. Struts takes time and maybe some guidance. Spring is, by far, the most complex, but when you learn how to use it to its full potential, you will be heavily coveted.
Update: Oh, and don't put you have 'spring experience' at the top of your resume, then not have it in any of your work experience of hobbies. You have spring experience? Where? How?