Now that Oracle has divorced Java EE, do you see a possibility of Spring merging with Java EE as one platform in the near future. Would such an outcome be in the interest of progress, unity and simplicity to the general Java community?
Or to the contrary, would it hurt one framework and boost the other, or maybe cripple or slowdown both?
I would like to take this opportunity to thank Kathy and Bert. Your programmer certification book SCJP6 drilled the foundations of Java into my DNA. It is a blessing to the Java community that you have continued with this noble cause of culturing new Java professionals even with the new Java edition releases. Thank you.
I would like to take this opportunity to thank Kathy and Bert. Your programmer certification book SCJP6 drilled the foundations of Java into my DNA. It is a blessing to the Java community that you have continued with this noble cause of culturing new Java professionals even with the new Java edition releases. Thank you.
Sorry i have just seen your post. Hope my response is still relevant.
Usually it's what we learn from the questions we get wrong (and right) on the practice exams that count.
However if i can offer my opinion purely on the scores you've posted i should say you may just get a fair amount of marks above the passing score (73%).
To be certain of passing with chances of a handsome score you should at least score marks in the region of 90% in 3 mock exams. Again there are no "hard rules" but am not completely off-the-mark with my advice.
Have you tried that code in the test harness which Tim posted at the beginning of this thread? It failed when I tried it.
Yes. It fails on the second test sentence by 1 word "i". Despite passing the first test sentence the code has a flaw (it's searching for patterns even in-between words).
Am working on a version that sticks solely to space-delimited words. It would be so far a unique solution if i pull it off. Thanks for pointing this out.
I.Y.O Are there enough and practical real-world justifications out there to warrant support in the JPA 2.x spec for keying on embeddables (rather than first class entities) when mapping key/value pair collections to relational data stores? Was this move more about 'completeness' than promotion of best design/coding practice? What's your take.