job listings are not set in stone I've noticed. The requirements are often more a wishlist than a firm requirement, and will list skills that are impossible to all aqcuire together at the age of the people they're looking for (or even in the timeframe all those techs have been on the market). Having a well ballanced portfolio of skills is more important to land a good job. A good will let you exploit your strengths while making sure you have opportunity to work on reducing those weaknesses where possible within the project architecture. EJB for example is nice and often listed as a requirement, but I've never used it and got asked for a lot of interviews where it was listed. I do have some theoretical knowledge about it which helps, but IMO it's usually the wrong choice for a project (which doesn't always help...).
WHAT is your favorite color? Blue, no yellow, ahhhhhhh! Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop