You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2013/05/21 23:14:20 UTC
[jira] [Updated] (OFBIZ-5183) Using require-new-transaction=true in
a service called (maybe not directly) by a pre-invoke or earlier event is
not yet suported in OFBiz
[ https://issues.apache.org/jira/browse/OFBIZ-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux updated OFBIZ-5183:
-----------------------------------
Description:
I got bitten by this TODO in ServiceDispatcher.runSync()
To set timeouts in OFBiz for services called inside of other services you have to add the <<require-new-transaction=true>> attribute to the called services definitions. This has a side effect in some cases. Because of a non completed feature in OFBiz:
{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}
Of course, using ECA called async will have the same effect (not in title)
Note: "pre-invoke and earlier events" are preprocessor, firstvisit and so on
was:
I got bitten by this TODO in ServiceDispatcher.runSync()
To set timeouts in OFBiz for services called inside of other services you have to add the <<require-new-transaction=true>> attribute to the called services definitions. This has a side effect in some cases. Because of a non completed feature in OFBiz:
{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}
Of course, using ECA called async will have the same effect (not in title)
> Using require-new-transaction=true in a service called (maybe not directly) by a pre-invoke or earlier event is not yet suported in OFBiz
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> 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()
> To set timeouts in OFBiz for services called inside of other services you have to add the <<require-new-transaction=true>> attribute to the called services definitions. This has a side effect in some cases. Because of a non completed feature in OFBiz:
> {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}
> Of course, using ECA called async will have the same effect (not in title)
> Note: "pre-invoke and earlier events" are preprocessor, firstvisit and so on
--
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