Advice from various people

Best posts (imho) from JavaRanch with advice on the exam.

  • Few of these mention the Companion text, but all have recommended the Head First text
  • All have mentioned Enthuware
  • At least three posts mention custom tag questions not appearing on their exams (no guarantee though)

More here: OCEWCD Wall Of Fame



* Head First Servlets and JSP: Passing the Sun Certified Web Component Developer Exam 2nd Edition - covers 5, rather than 6, but still a highly recommended resource. Of course, you'll need another resource for Java EE 6. The authors actually wrote the 1.5 version of the exam, so you'd be silly to skip this. Book web site and errata - definitely check this for mock exam


* OCEJWCD Study Companion: Certified Expert Java EE 6 Web Component Developer (Oracle Exam 1Z0-899) 3rd ed. Edition


* Java Practice Questions: Oracle Certified Expert, Java EE 6 Web Component Developer

Assumptions for the exam

These are exactly the same as for the OCA and OCPJP exams:

  • Missing package and import statements: If sample code do not include package or import statements, and the question does not explicitly refer to these missing statements, then assume that all sample code is in the same package, and import statements exist to support them.
  • No file or directory path names for classes: If a question does not state the file names or directory locations of classes, then assume one of the following, whichever will enable the code to compile and run:
    • All classes are in one file
    • Each class is contained in a separate file, and all files are in one directory
  • Unintended line breaks: Sample code might have unintended line breaks. If you see a line of code that looks like it has wrapped, and this creates a situation where the wrapping is significant (for example, a quoted String literal has wrapped), assume that the wrapping is an extension of the same line, and the line does not contain a hard carriage return that would cause a compilation failure.
  • Code fragments: A code fragment is a small section of source code that is presented without its context. Assume that all necessary supporting code exists is present and that the supporting environment fully supports the correct compilation and execution of the code shown and its omitted environment.
  • Descriptive comments: Take descriptive comments, such as "setter and getters go here," at face value. Assume that correct code exists, compiles, and runs successfully to create the described effect.