Some of the reactions to my post "Are Plain Old WebContainers still appropriate in Java EE 5?" implied, that it could be hard to integrate "legacy" POJOs with plain EJB 3 technology. To clarify this issue, I tried to deploy a really "legacy" POJO as a Stateless / Stateful Session Bean. ...I tried to deploy an already existing class - the javax.swing.table.DefaultTableModel as a Session Bean (!!!), without changing the source code. The deployment (to Glassfish v2), as well as test worked (!!!). It's interesting, but many developers think, that EJB 3 can only works with annotation - or bloated deployment descriptors...The read entire entry: http://www.adam-bien.com/roller/abien/entry/ejb_3_0_and_legacy
Blogs: Swing's TableModel in EJB 3.0
Adam Bien provides an overview -- including code listing's -- on how to wrap Swing's TableModel as an EJB 3.0 stateless session bean.
- Posted by: Daniel Rubio
- Posted on: October 18 2007 12:37 EDT