[seam-dev] Re: Blocked threads
Dan Allen
dan.j.allen at gmail.com
Fri Jun 6 00:08:27 EDT 2008
>> I think we should only disable the (Transaction interceptor) *if* transaction >> management (Seam-managed global trasaction) is being used. If not, then >> we have no transaction at all on the call.
>>
>> Init.instance().isTransactionManagementEnabled()
>
> Sure, but this is pretty low priority as most people use SMT. JIRA please.
I plan to followup on the transaction JIRA issue that is going to be
filed. However, keep in mind that while transaction management might
handle JSF requests, there are ways to invoke Seam components
*outside* of a JSF request (Seam remoting for instance). In those
cases, we need the TransactionIntercepter. Let's just be careful not
to over do it.
--
Dan Allen
Software consultant | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
NOTE: While I make a strong effort to keep up with my email on a daily
basis, life and work come first and, at times, keep me away from my mail
for a while. If you contact me, then don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
More information about the seam-dev
mailing list