Hi,
Please see my comment on this issue at:
http://forums.java.net/jive/thread.jspa?threadID=13366&tstart=0
In my EJB3 Demo project (
https://ejb3demo.dev.java.net/) I am exploring
patterns that allow maximum reuse of code, and protect investment in
code. I therefore want to come up with coding style that uses EJB 3.0
but makes J2EE redundant - if you know what I mean. I think that the
greatest value of EJB 3.0 is that it promises a POJO style programming.
What that means to me is that I should be able to use the same
components inside and outside a J2EE container. If EJB 3.0 fails to
achieve this, it will never capture the minds of those who believe in
alternative frameworks like Spring Framework that do support POJOs.
Regards
Dibyendu