So, do you think this change is OK or do you think the change should be
rollbacked (revert to the EVENT scope) and another solution should be
investigated to solve JIRA-4542?
On 06/04/2010 05:41 AM, Pete Muir wrote:
In that case you need to disable Seam Managed Transactions (see the
ref guide for more).
On 3 Jun 2010, at 19:44, Steve Roy wrote:
> 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.
> - steve
> On Thu, Jun 3, 2010 at 1:44 PM, Pete Muir<pmuir(a)redhat.com> wrote:
> I'm slightly (sorry, that's irony ;-) concerned about this, it just seems
wrong. System transactions are request scoped in Seam.
> Why do we need to do this?
> On 3 Jun 2010, at 17:08, Denis Forveille wrote:
>> Recently, to address JIRA-4542
) , the scope of the
>> EjbSynchronizations component has been changed from EVENT to SESSION.
>> I'm worrying about the impact of such a change on the behavior on Seam
>> Is this change safe? Is there really no impact on the applications?
>> Please have a look at JIRA-4542 for more details
>> seam-dev mailing list
> seam-dev mailing list