On Tue, Nov 24, 2009 at 3:44 PM, Gurkan Erdogdu <gurkanerdogdu(a)yahoo.com>wrote:
Actually OpenEJB works great as an embeddable.
Just dowloand openejb.war, deploy it into tomcat/webapp that is it! You can
use all EJB container functionality in your web applications!
Great news. That's the simplicity we need to offer (or else we just lose
people).
Actually the point is that EJB is just a technology related with Java EE
distribution model/architecture. Its usage heavily depends on where you
would like to use it. If you want to create a (simple) web application that
depends on single database resource, maybe it is not necessary to include
EJBs into your application. But if you would like to use 2PC (for example,
integrating JMS with Databases etc.), to distribute your business code into
more than one machine , to integrate with legacy CORBA systems or other
messaging systems etc. you could likely to use EJBs in Java EE environment.
Yes and no. What we are doing is forcing EJB on people that want a
transactional bean. That's really the problem that I see.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen