[ https://issues.apache.org/jira/browse/OFBIZ-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638935#comment-13638935 ]
Jacques Le Roux edited comment on OFBIZ-5183 at 4/23/13 1:20 PM: ----------------------------------------------------------------- I see three possible steps # For now, comment in the require-new-transaction documentation in services.xsd, to prevent bad surprises # Allow the functionnality to work as currently designed. This is a mod terms solution to be investigated. # Allow to put a timeout in any service withouth having to use require-new-transaction. I guess this one is certainly a long term solution... was (Author: jacques.le.roux): For now, this should be at least commented in the require-new-transaction documentation in services.xsd > Allows ECAs related to services with require-new-transaction=true in > pre-invoke and earlier events > -------------------------------------------------------------------------------------------------- > > Key: OFBIZ-5183 > URL: https://issues.apache.org/jira/browse/OFBIZ-5183 > Project: OFBiz > Issue Type: Bug > Components: framework > Affects Versions: Release Branch 10.04, Release Branch 11.04, SVN trunk, > Release Branch 12.04 > Reporter: Jacques Le Roux > Priority: Minor > > I got bitten by this TODO in ServiceDispatcher.runSync() > {code} > // TODO: if there is an ECA called async or in a new transaction it won't get > rolled back > //but will be called again, which means the service may complete multiple > times! that would be for > //pre-invoke and earlier events only of course > {code} > I will try to have a look -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira