It was the biggest JAX conference so far. Also the first time the organizer had to "close" my workshop: Java EE 6 Follow Me - You Can because of AttendeesOverflowException.The workshop was amazing. The developers were eager to develop along with me an EnterpriseRoyalWedding application. We had to discuss 2PC (only then you really understand the wedding-transaction) and built together an application with REST,transactions, events, multi-stage configuration, SOAP (was asked for that), unit tests, load tests and many attendees questions. I was asked to push the code on every break to http://kenai.com/projects/javaee-patterns and announced the URL via twitter @AdamBien. The most popular question in the whole workshop was: "Please show me the index.html again". It seems like the whole Java EE 6 stuff was trivial to understand :-)

In the session Session: Some Java History: from JDK 1.0 to 1.7 I presented my view of the history of Java. In the "Sun Java Studio 1.0" demo I presented what was possible in 1997. The software ran on JDK 1.1.3 and was crazy fast on my machine :-)

Every "pro"-blogger should write a post "Java Programming Language is Dead" this time to be taken seriously by the community. In the Session: Java is dead? No #1., I presented my opposite point of view: "Given you are pragmatic in your Java projects - it really rocks".
In the One Slide Session: 60 Minutes With Java EE 6 I developed the small version of RoyalWedding. I got many attendees questions regarding CDI / ManagedBeans / EJB 3.1 so I sticked with the topics.

Problem is: if Adam quote the name of my pattern, then this blog would require a FSK-18 tag ;)

Oki, to 'roughly' translate it: it's about the bad praxis that big companies rather like to have JBoss4, Weblogic8 and the likes of old Java1.4 origined irons than to upgrade to newer EE servers.

Thus developers are forced to 'make them naked' via stripping em down to a naked tomcat by either inverting the classloader hierarchy (client classloader first) or completely disabling almost all of the jars of the EE server at all. You basically end up with 350MB of EE server jars, but only use the naked tomcat jar from it (4MB).

The sad part: this happens to 60-80% of all older EE servers I've seen, which is imo a serious threat to operating centers.

The managers feel safe because 'all is standard Weblogic8', but if you look at all the various spring, hibernate, jsf, whatever jars in the deployed webapps then you clearly see that it's much worse than if they would just use tomcat or up2date EE servers for newer projects.