J Deckarm wrote:chapter 15, page 907
"Unlike prepared statements, stored procedures and functions must exist before a CallableStatement can be executed on them."
=> This sentence seems to be somewhat confusing; sounds as if CallableStatement would execute PreparedStatement as well
J Deckarm wrote:chapter 15, page 923
"A transaction includes all of the SQL queries you execute until either..."
=> While it might be a terminology debate, "queries" could seem to indicate SELECTs only.
Mark Kevin wrote:On the fifth line down on page 145, in the comment, isn't the static variable named frogCount, rather than FrogCount?
Mark Kevin wrote:I could be wrong, but on page 145, in the big paragraph in the top half of the page, I see references in three places to the 'static method' but all I see in the preceding code is a static variable, frogCount. Where is the static method the text refers to? Sorry to bother you.
J Deckarm wrote:chapter 14, page 818
"A ForkJoinTask has many methods (most of which you will never use), but the following methods are important: compute(), fork(), and join()"
=> This might be somewhat misleading, because the compute() methods are in fact not in the ForkJoinTask class itself, but its subclasses RecursiveTask and RecursiveAction
J Deckarm wrote:chapter 12, page 698
The example would seem more complete if in class Bar the doStuff(Foo f) method would have a body of calling f.foof(); so that the overriden method would be really utilized
J Deckarm wrote:CD mock exams, objective 6, OCP Exam 1, question 6
Answer E states "Never throw an AssertionError explicitly" is not marked as a correct answer, yet in the explanation it states "throwing an AssertionError explicitly is considered bad practice"
J Deckarm wrote:chapter 12, self-test q6
explanation says: "The variable referenced by f is an instance of an anonymous subclass of Bar..."
=> Should be rather likely "The object referenced by the variable f..." (just as two sentences earlier regarding variable t)
Mark Kevin wrote:K & B, OCA 7, page 192
In the middle of the page, shouldn't:
In other words, 'a' should be 'a1' ?
J Deckarm wrote:CD mock exams, objective 1, OCP Exam 1, question 2
While the explanation seems to be a valid statement, the compilation seems to fail on the first place because of super cannot be used in a static context; regardless whether the method in the parent class is static or non-static
J Deckarm wrote:chapter 10, page 571, answer 5
"Not shown is a class implementing class G that actually creates the object."
=> Should be likely "extending class G"
J Deckarm wrote:CD mock exams, objective 3, OCP Exam 1, question 3
Answer C states: "IS-A relationships always require at least two class types"
J Deckarm wrote:CD mock exams, objective 3, OCP Exam 1, question 4
answer B is marked as correct: "HAS-A relationships always rely on instance variables"
J Deckarm wrote:chapter 7, page 395, table 7-3
"Java 7 with duplication" row "What happens if rain() adds a new checked exception?" case says to "Add another exception to the multi-catch block to handle the new exception."
J Deckarm wrote:In general, the entire table seems to would worth reviewing and all possible cases described
J Deckarm wrote:chapter 4, page 255
question 7 is related to enums, OCP objective 2.5, which is not listed beside the answer (it is mentioned at the question itself on page 252)