One of the main issues I had with Seam 2.x was the (lack of) tx propagation support options (specifically REQUIRES_NEW and NOT_SUPPORTED) when using @Transactional when compared with EJB3 tx support and Spring tx support.<br>
<br>Refer to this thread: <a href="http://sfwk.org/Community/TransactionalPropagationTypes">http://sfwk.org/Community/TransactionalPropagationTypes</a><br><br>and this: <a href="https://jira.jboss.org/jira/browse/JBSEAM-595">https://jira.jboss.org/jira/browse/JBSEAM-595</a><br>
<br>and this: <a href="https://jira.jboss.org/jira/browse/JBSEAM-4391">https://jira.jboss.org/jira/browse/JBSEAM-4391</a><br><br>AFAIK this is not fixed and/or released. Will this be fixed and released with Seam3?<br><br>
<br><div class="gmail_quote">On Tue, Nov 24, 2009 at 12:44 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.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;">
Btw, this is exactly why most people use Seam 2. They don't want to deal with EJB. They can just annotate with @Name and inject a Seam-managed persistence context. The transactions are hooked into whatever they want: local, JTA or Spring. It's "the hell with EJB" approach.<br>
<br>I'm just saying perhaps we can find a way to cater to this approach in Java EE so we don't lose those people to the platform.<br><font color="#888888"><br>-Dan</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Tue, Nov 24, 2009 at 3:41 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.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;"><br><div class="gmail_quote"><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
It's somewhat related....in terms of Resin, we actually don't have such<br>
a thing as a traditional EJB container - we have "aspects" such as<br>
transactions delivered via meta-data (e.g. @TransactionAttribute), the<br>
aspects are bound to an underlying implementation (e.g. transaction<br>
manager) and can be used in any component model including managed beans<br>
or EJB. The "EJB Lite" distinction is tenuous since you don't really<br>
need to use the EJB component model per se.</blockquote></div><div><br>To be honest, I'm kind of confused myself now. Circling back to my initial argument, the two options we provide in Java EE at this moment are:<br>
<br>- a non-transactional "simple" managed bean or,<br>
- an EJB session bean (which is, by default, transactional, and more)<br><br>So if the developer wants a transactional bean without using an EJB container, they have to use some sort of framework (or portable CDI extension) to get it. To me, that is where Java EE falls apart. There needs to be some middle of the road that the developer can get a transactional bean out of the box OR we just need to say, if you want a transactional bean, you have to use EJB w/ at least EJB lite, period.<br>
<br>Why isn't the "simple" transactional bean something that Java EE can provide. Clearly a use case is being ignored.<br><font color="#888888"><br>-Dan<br></font><br>p.s. The "simple" transactional bean would be a bean w/ @TransactionAttribute and somehow @PersistenceContext would be supported on the bean.<br>
</div></div><br>-- <br><div><div></div><div>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</div></div><br>_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br></blockquote></div><br>