On 27/08/2010, at 11:25 AM, David E Jones wrote: > On Aug 26, 2010, at 5:13 PM, James McGill wrote: > >> On Thu, Aug 26, 2010 at 2:43 PM, James McGill < >> [email protected]> wrote: >> >>> >>> https://issues.apache.org/jira/browse/OFBIZ-3903 >>> >>> >> I found that by adding TransactionUtil.rollback(); after seeing an error >> result from the Dispatcher, I can at least hide the problem. > > It looks like you're getting into why this happens. Screen rendering is done > within a big single transaction. If you want parts of the screen to fail > independently of other parts of the screen, they need to be in a separate > transaction (ie pause the original, start new, commit/rollback new, resume > original). Just rolling back a failed transaction and leaving the rest of the > screen hanging is probably not a good idea. > > -David
Perhaps we should add a require-new-transaction attribute to the screen element? Regards Scott
smime.p7s
Description: S/MIME cryptographic signature
