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

Ok, so why did we not do it so that the jBPMContext component is cleaned up before ejbSynchronizations? On 4 Jun 2010, at 12:27, Jozef Hartinger wrote: > Note that the modification primarily addresses JBPAPP-3764 > https://jira.jboss.org/browse/JBPAPP-3764 > > > On 06/03/2010 06:08 PM, 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(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev