[seam-dev] Impact of the change of scope (EVENT to SESSION) of the EjbSynchronizations SFSB component?

Pete Muir pmuir at redhat.com
Thu Jun 3 13:44:23 EDT 2010


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:

> Hi,
> 
> Recently, to address JIRA-4542
> (https://jira.jboss.org/browse/JBSEAM-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
> applications
> 
> Is this change safe?  Is there really no impact on the applications?
> 
> Please have a look at JIRA-4542 for more details
> 
> Thx.
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev




More information about the seam-dev mailing list