Happy Book Birthday! OCP 17 Practice Tests

Our Java 17 Practice Tests book has been released! This is a major rewrite of our Java OCP 11 book with hundreds of new and revised questions! If you already have our Java 17 Study Guide, you can purchase it individually, or you can buy it as kit.

The Practice Tests OCP 17 book contains 11 chapters helping you review and reinforce each objective. It also includes 3 full practice exams. All questions in the practice test book are unique from those in the complete study guide.

my first ever time on the big stage at javaone

Every year, JavaOne has a community keynote. Last time, it included a skit for a lot of people in the Java community. This year, it was a number of segments. I was asked to be in one about Java authors. Maurice Naftalin and I each got to answer two short questions about writing/our books. Mine were

  1. Why did you decide to write a book?
  2. How does studying for the certification exam

We were given the questions in advance so we could have a prepared succinct answer. While the answer was content reviewed, we didn’t have to stick to it word for word.

The keynote was on the main stage and quite a production. It was really cool to see the behind the scenes. They even had a make up person to ensure everyone looked good on camera.

I speak twice for about a minute each at the timestamps in each of these videos:

And then at the end everyone who spoke at the community keynote got to go back on stage at the end. This video is that moment timestamped.

[2022 javaone] jakarta ee panel

Speakers: Will Lyons (Oracle), Edwin Derks (Rockstars IT), Emily Jiang (IBM), Reza Rahman (Microsoft), Ivar Grimstead (Eclipse Foundation)

For more see theĀ table of contents

Jakarta 10

  • Lots of projects released
  • CDI Lite is new spec but subset of CDI so not completely new
  • Core profile – targets restricted environments
  • Java 11 source/binaries

Q&A

  • Emphasis on opinions, community needs to weigh in
  • Looking forward to Loom
  • Release cadence need to be adopted by community. Cadence of spec itself being too fast risks not having proper adoption.
  • Need enough contributions to have a release
  • At one point had goal of yearly release cadence
  • Hard for customers to update that often
  • Room survey was 50/50% on one vs two year release cycle for Jakarta EE
  • Could release pieces independently. Could be confusing
  • A lot of companies align with Java SE LTS cycle
  • Vendors can certify against LTS versions
  • log4j has caused more patching
  • Companies will keep skipping versions
  • Room survey: people using a variety of EE versions
  • Demand vs capacity to deliver
  • Emily working on a one pager on how to contribute. Already have English doc https://jakartaee-ambassadors.io/guide-to-contributing-to-jakarta-ee-10/
  • https://github.com/jakartaee
  • “If there’s something you want, create a feature, now you are a contributor”
  • need to be able to explain why to contribute

My take

I like that there was a lot of time for audience comments and sharing opinions for the audience and panel. The brief prepared remarks set the stage well for that.