Yesterday, I attended the second Glassfish Unconference. Similar to last year, this unconference precedes CommunityOne which precedes JavaOne.
I like the concept of the unconference, as an attendee you have influence in the agenda and direct participation is encouraged. For me, this is a possibility to talk with the Glassfish team leaders, and to estimate the enthusiasm that is in the project.
After the Sun-Oracle deal was announced, there was some fear that Oracle might stop Glassfish support. There aren't too many people who know what is going to happen, and the best thing the Glassfish team can do now is to move on and deliver a high-quality software product.
I think it is very valuable that the Glassfish team tries to keep a good contact with the developer and user base. For me, this is one of the reasons why I prefer developing my applications on Glassfish: it doesn't feel that I deploy the applications on a black box, it is deployed onto a piece of software that is pretty familiar and very open.
I was pleased to hear that the OSGi integration is now also available in the EJB container, and that you can call OSGi services from the EJB container. That opens lots of possibilities. I have to play with it as soon as I get some time.
The Java EE spec itself is becoming more modular as well. Indeed, people are always asking for more stuff in the Java EE spec, and that leads to a huge spec. Typical applications only need parts of the functionality offered by the specification. Different "profiles" inside the Java EE spec might help.
At the end of the day, people could chat informally at a party in the Thirsty Bear. I could see that the Glassfish team leaders and developers are still very motivated.
written on 01 Jun 2009 16:58.Create comment