[ http://issues.apache.org/jira/browse/OFBIZ-333?page=comments#action_12443087 ] David E. Jones commented on OFBIZ-333: --------------------------------------
This new patch is better in that it avoids changing that interface. I'd still like to opinions from other people about where to put the attribute though. To me it makes more sense to put it with the other transaction attributes in the service definition. Heck, if we put it there it might even be useful for other things like other places where a service might be called multiple times... > ServiceMultiEventHandler to support configurable global transaction > ------------------------------------------------------------------- > > Key: OFBIZ-333 > URL: http://issues.apache.org/jira/browse/OFBIZ-333 > Project: OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: framework > Reporter: Si Chen > Attachments: ofbiz-333.2.patch, ofbiz133-1.patch > > > This is a continuation of OFBIZ-201: the ServiceMultiEventHandler will be > enhanced to support configurable global transaction. This will be done by > adding a "global-transaction" attribute to the event tag: > <event type="service-multi" path="" > invoke="quickScheduleShipmentRouteSegment"/> > for global-transaction="true|false" which defaults to true. If > global-transaction="false" then there will be no TransactionUtil.begin(..) > and commit(..) around the services calls. Instead, each service will be > called with its own transaction, and whatever messages it returns will be > added to a List of messages to be sent back to the request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
