<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:10pt"><div>>>>What we are doing is forcing EJB on people that want a transactional bean. That's really the problem that I see.<br>Yeap, this is a problem and mistake. Besides, EJB technology is much more than transactions.(security, pooling, clustering, integration, messaging etc.)<br><br>Also, *transaction* is a generic term. Java EE defines distributed transactions over JTA and JTS specifications. Web containers do not required to implement those specifications. <br><br>If you do not like to use EJB transaction demarcation model, there are several choices that people can use for their web applications<br><br>1* Manage your JTA transactions over third party Transaction Managers<br>2* Give up it to the Java EE containers.<br>3* Do not use JTA, then manage your JDBC connections with your own
solutions or some third party libraries<br><br>But each one has also an advantage or disadvantage? If you look at EJB 3.1 specification, it is very very easy to integrate lots of cool functionality into your application.<br><br>Thanks;<br><br>--Gurkan<br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Dan Allen <dan.j.allen@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Gurkan Erdogdu <gurkanerdogdu@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b> reza_rahman@lycos.com; Weld-Dev <weld-dev@lists.jboss.org><br><b><span style="font-weight: bold;">Sent:</span></b> Tue, November 24, 2009 10:46:34 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [weld-dev] persistence and transactions
outside Java EE<br></font><br>
<meta http-equiv="x-dns-prefetch-control" content="off"><div class="gmail_quote">On Tue, Nov 24, 2009 at 3:44 PM, Gurkan Erdogdu <span dir="ltr"><<a rel="nofollow" ymailto="mailto:gurkanerdogdu@yahoo.com" target="_blank" href="mailto:gurkanerdogdu@yahoo.com">gurkanerdogdu@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><div>Actually OpenEJB works great as an embeddable.<br><br>Just dowloand openejb.war, deploy it into tomcat/webapp that is it! You can use all EJB container functionality in your web applications!<br>
</div></div></div></blockquote><div><br>Great news. That's the simplicity we need to offer (or else we just lose people).<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><div><br>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.<br>
</div></div></div></blockquote><div><br>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.<br><br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br><br><span><a target="_blank" href="http://mojavelinux.com">http://mojavelinux.com</a></span><br><span><a target="_blank" href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a></span><br><span><a target="_blank" href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a></span><br>
<meta http-equiv="x-dns-prefetch-control" content="on"></div></div>
<!-- cg17.c1.mail.mud.yahoo.com compressed/chunked Tue Nov 17 21:32:47 PST 2009 -->
</div><br>
</body></html>