I am very pleased to share with you that the JavaOne 2015 content is now fully finalized and published. In this brief but detail-rich blog entry I want to tell you a little bit about the Java EE content. As a reminder, JavaOne 2015 is going to be held on October 25–29 in San Francisco and you can register here.
Thank You, Regrets and Being Persistent
First and foremost I want to thank everyone that took the time to submit carefully crafted proposals to the Java EE track. Your passion and dedication has helped us construct a very strong offering for the community at large. It was a privilege to review all your sessions. JavaOne is a key part of the global Java community far beyond the walls of Oracle and all of you are a large part of keeping it successful. This year we are proud to say we have been able to minimize Oracle speakers again in favor of folks from the community as well as real world stories from your fellow Java EE users.
I want to especially thank the folks that did not get sessions accepted, I ask that you don't get discouraged and I hope that you still consider coming to JavaOne. Not getting a session accepted doesn't mean your proposal wasn't great - it simply means the track was fortunate enough to have submissions this year that perhaps were a better fit in one way or the another. It is all the more reason to further sharpen your proposal and try again next year.
Some Key Content
Following are some of the key Java EE sessions that got accepted, broken down by some useful but arbitrary categories. The full content catalog is available here. You should take a look at the catalog and perhaps book your sessions before they fill up.
Java EE 8: One of the unique value propositions for JavaOne is that it is the best place to learn about what is ahead in terms of standard Java technologies right from the source - the spec leads themselves. We were able to put together a number of such sessions. You should take advantage of these sessions not just to stay informed but to engage.
Best Practices/Design Patterns: Beyond learning Java EE APIs, it is critically important to understand how to effectively apply them in real life applications, which is where best practices and design patterns come in.
Real World Adoption Stories: As we grow the Java EE community it is more and more important to highlight adoption stories, case studies and migrations from other technologies. Last year was very good in this regard and I am happy to say this year is even better. In fact there were a number of such submissions that we could not accept this year that we hope will be resubmitted in the coming years.
The Java EE Ecosystem: The ecosystem that builds upon Java EE APIs is critically important in keeping the platform strong. This year was far better in this regard than previous years. We always hope to highlight such content and wish there were more submissions along these lines.
Fostering Java EE Community Speakers
One of the key reasons attendees come to JavaOne is to hear from Oracle's Java technologists. Unsurprisingly the most well attended sessions tend to be led by Oracle speakers. This year we have the usual strong showing of Oracle speakers: David Delabassee, Geertjan Wielenga, Bill Shannon, Linda Demichiel, Ed Burns, Manfred Riem, Santiago Pericasgeertsen, Nigel Deakin, Heather Vancura and Mark Heckler just to mention a few. In order to continue to grow the Java EE community however it is vitally important to foster a greater number of community speakers that advocate Java EE. While this has gotten much better over the years, we need to do more at JavaOne to encourage speakers to take up Java EE as a topic. These are just some of the community speakers that we are very proud to host this year:
I hope to see you all at JavaOne. In the next coming weeks and months we will be sharing more details on the Java EE track, content and speakers at JavaOne. Lastly having been on the other side of the fence I know as much as you might come to JavaOne, it might not be a practical reality for you for a variety of good reasons. I want to remind you that we make a point to make JavaOne content openly available to all. That being said I want to tell you that you should make the pilgrimage to JavaOne at least once as a Java developer. I have attended it a total of eight times, most often paying out of my own pocket as a self-employed consultant.