What it takes to become an Enterprise Java Developer?
An exhaustive and comprehensive list of items that a (true) enterprise Java developer should know. I would like to brief the items here with my own rating of importance, however, you can point to the title of this post for a detailed explanation.
- OOAD, UML (highly desirable)
- Java Core Libraries (must)
- Understand JVM, classloading etc. (desirable)
- AWT, Swing/JFC for desktop clients. (optional)
- JDBC API (MUST)
- Java security models and APIs. (desirable)
- Servlet, JSP, JSTL (MUST)
- Web/Application servers (MUST)
- Web frameworks (optional but desired)
- XML and Parsers (highly RECOMMENDED)
- Other J2EE APIs/Concepts (highly recommended)
- EJB (Highly Recommended)
- Aspect oriented programming/AOP (optional)
- JNI (optional)
- JCP/JSR/Data mining etc. (optional)
- JUnit (MUST)
- Ant, Maven etc. (MUST)
- Software Engineering processes (Highly Recommneded)
Do check out the full information at "Journey to Java" weblog at the title of this post.
[Resource-type: Weblink/blog-post; Category: Java/J2EE; XRating: 4]








1 Comments:
That's a pretty good list! It pretty much matches what I ask for when I'm interviewing for an Enterprise Java developer.
The ability to be able to set up web and app servers etc cannot be underestimated!
9:56 AM
Post a Comment
<< Home