Simon Zambrovski

I had a chance to speak about Eclipse Common Navigator Framework on Eclipse DemoCamp Hamburg – Galileo Edition. The event was a full success. Five speakers and fourty visitors were attending. After the formal part, there was an opportunity to relax at the bar of East Hotel Hamburg, thanks to Peter and Martin.

My talk was focussed on the basics of CNF. After some slides on Why, What and How, I moved on to a live coding demo and coded a small CNF view inside of an trivial RCP. Everithng worked fine, until the launch – I misspelled one id in the plugin.xml, and had to resign and showed the prepaired result instead of the hacked one. If you want to read more, check out the TechJava report.

The Galileo Edition of Eclipse is already in the pipeline and the community is happy to celebrate this with a series of events. In Hamburg we do it in two ways – there are Eclipse DemoCamps and Eclipse Stammtisch. This time Peter and Martin managed to put both events together. To make it short:

• What: Eclipse DemoCamp + Eclipse Stammtisch
• Where: Hotel East, Hamburg ( Simon-von-Utrecht-Str. 31, 20359 Hamburg, Germany)
• When: May 25th 2009, 18:00-21:00 (official part)

I’m attending. If you want to attend, make sure you find a minute to write you name down in EclipseWiki.. If you want to read more, look at the original post at TechJava…. See you on the DemoCamp.

Yesterday, the second Adam Bien event in Lehmanns Bookstore took place. Again, the event was a full success. I arrived half-an-hour earlier and got a seat only in the tenth row. Adam spoke about new features of EJB 3.1 and Glassfish. He showed examples running on a developer build of Glassfish V3, promising that the features will work without exceptions… Here are some topics, I remember:

• Singleton Beans: usefull a s a central point of the application, e.G. central cache etc…
• Async Methods: allows asynchronous execution of time-consuming methods. Especially, it is possible to abort the execution
• Deploying Beans in WARs: could be helpful for small applications
• Global JNDI-Namespace
• No interface view: simplifies the access to beans, if needed
• EJBCOntainer.getEJBContainer().getContext(): allows external initialization of bean context, which is nice for testing

Later, Adam discussed some Core J2EE patters, that become absolete with EJB 3.1 and others which are still valid. After the talk, I spoke with Adam about the OSGi as a module architecture inside JEE application, which seems interesting to me. The pictures are as usual available in my FlickR Gallery.