This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
An add just saying "JEE" is sloppy. JEE includes JDBC (arguably), JPA, Servlets, JSP, JSF, JMS, EJB, etc. A company almost never wants all of these.
Thank you Jeanne. I've worked a bit with JDBC, JSP, JSF (myFaces)...can't say I've done anything with Servlets, JPA, JMS or EJB.
Wonder if, given what I haven't worked with, when I see an ad with a 'J2EE' requirement, I should just skip over and not bother.
Hand-picking APIs while searching for job positions may not be the most effective way to get an interview. Programming experience with Java can be described in many different ways and there are many APIs that are critical to some applications and irrelevant others. "J2EE" is an old acronym that is not used to describe the current set of Java Enterprise APIs. If you find a job advertisement using J2EE, you should take special care to find out why they are using the outdated acronym and if they really are looking for someone with experience in the older APIs, as this may be the case.
I'm a senior architect/developer in the J2EE "space" where I work.
I also assist in the requirements and recruitment process.
What we (here, not everyone) really looks for in terms of J2EE is:
Do you understand MVC?
Can you name technologies used in each layer?
Do you know what a JSP is? (We don't have JSF... yet ;))
Name some HTTP requests, and their difference.. GET,POST etc.
Name some ways to connect to a database.
What is the role of an application server?
Then the usual J2SE suspects, GC, collections etc..
You don't necessarily have to know all the APIs, but if you put JMS on your resume, be prepared to discuss it and answer questions!
author & internet detective