Java EE 6 And Rethinking - JUG HH Afterglow
I really enjoyed the session at Lehmann's (cool book store with impressive amount of not only Java books). It was organized by JUG in Hamburg. We had interesting, late night, discussions - and finally some consensus:
- DAO is not completely dead - only in the majority of all cases :-).
- EJB 3.1 are lighter than expected
- Wicket is cool and JSF just works - especially with EJB 3.1.
- OSGI inside the applicationserver could solve some interesting problems in HA and highly dynamic environments.
- Layering is not always good.
- WAR deployment of no-interface beans is interesting for small web apps with databinding...
- Async methods are interesting - especially in case they can be monitored and managed by the appserver.
- Singletons are interesting for pre-initialization etc.
- ...and other stuff - it was finally to late.
Regarding point 7:
You mentioned that Async methods can be taken into account as an alternative to JMS in some circumstances. I fully agree with that and want to give just a little remark:
I can imagine that it would be more "light weight", i.e. will use less resources as JMS and so can be faster and/or more compact. That is because of the implementation on the basis of the Future mechanism and such stuff is running only in memory whereas JMS is using Databases (at least I do not know of another way).
Okay, the Async feature will certainly not support recoverable transactions or persistent states which will be recovered after a server crash-and-restart, hence will not guarantee the processing of the method, but many asynchronous tasks don't need such "recoverablility".
Posted by Ronald on September 18, 2008 at 11:37 AM CEST #