Recovering from JavaOne 2010
I had originally planned to write a blog post per day during JavaOne 2010. That being my first JavaOne I was of course completely unprepared for the hectic routine of sessions, meetings, parties and more sessions. I wrote blog posts in the first two days and disappeared ever since.
I am alive, well, and back to Brazil. I had a terrific time in San Francisco where I got to meet a lot of interesting people, some for the first time and some that I had previously known online. What explains my silence is the fact I got sucked into a new consulting assignment immediately after touching ground, and only now I have time to rest a bit and reflect on what I have seen.
JavaOne 2010 was all about The Cloud for me, and in many ways it changed my views as to what cloud computing really is about. I will have to write a post specifically about that in the future, but I am now convinced that the Cloud is an umbrella concept for a number of practices and technologies related to the simplification of system deployments ( in contrast to the more traditional view related to cost benefits from economies of scale). There were a number of very interesting announcements and demos related to Cloud Computing and I believe over the next year more and more Java-enabled cloud platforms will enter production stage ( and at some point after that we will see some common apis emmerging this space).
There was already a lot of coverage about the future of the Java platform, so I will skip the details here. The overall feeling I got is that in spite of concerns related to the JCP and the Google/Android lawsuit the Java platform is in good hands with Oracle. The JavaOne keynote was very efficient in making the imediate direction clear. I agree with some things ( like splitting Java 7 into 7 and 8 ) and don't understand others ( javame.next and JavaFX) but the important message is that the Java platform will be moving forward again, which is a good thing.
In the Java EE space there were no big new announcements. Instead, there was a renewed commitment with the development of Glassfish as an open source product. That is fine by me: Java EE 6 is still seen as cutting edge by many organizations and has a long way to go before becoming obsolete. My top Java 8 wish ( EE apps as first class citizens in the JVM ) is not going to happen anytime soon, but was hinted to be somewhere in the future of Java EE. This is an area where Java EE and The Cloud intersect. I have seen some demos of PaaS clouds based on Java technology ( CloudBees and VMForce, among others) and I wonder how these services are planning to solve the problem of application isolation. Google has solved it in App Engine by using a custom JVM. If more and more companies go down this route we may end up with a fragmented Java ecosystem in the Cloud.
I was surprised in JavaOne 2010 to not find any sessions about Apache Wicket, my favourite web framework. In order to remedy this situation in JavaOne Brazil 2010, I have submited a session proposal about Wicket development in Java EE 6. Should it be accepted I will be presenting Apache Wicket and how it provides a presentation layer option that fits in the Java EE 6 philosophy even beter than JSF 2.