<div><br></div>Should a transactions really be started at that early of an entry point in application code? The application code may need to do many things before a database(or other resource) transaction is actually required.<div>
<br></div><div>- steve<br><br><div class="gmail_quote">On Thu, Jun 3, 2010 at 1:44 PM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm slightly (sorry, that's irony ;-) concerned about this, it just seems wrong. System transactions are request scoped in Seam.<br>
<br>
Why do we need to do this?<br>
<br>
On 3 Jun 2010, at 17:08, Denis Forveille wrote:<br>
<br>
> Hi,<br>
><br>
> Recently, to address JIRA-4542<br>
> (<a href="https://jira.jboss.org/browse/JBSEAM-4542" target="_blank">https://jira.jboss.org/browse/JBSEAM-4542</a>) , the scope of the<br>
> EjbSynchronizations component has been changed from EVENT to SESSION.<br>
><br>
> I'm worrying about the impact of such a change on the behavior on Seam<br>
> applications<br>
><br>
> Is this change safe? Is there really no impact on the applications?<br>
><br>
> Please have a look at JIRA-4542 for more details<br>
><br>
> Thx.<br>
> _______________________________________________<br>
> seam-dev mailing list<br>
> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote></div><br></div>