This change probably won't have any effect in the branch as the service
semaphore stuff was only added a couple of weeks ago, long after the branch was
done, and it's a new feature in the framework that shouldn't go into the branch.
Using it in the branch shouldn't cause things to not function, but there will
be a XML validation error every time the file is read.
-David
[EMAIL PROTECTED] wrote:
Author: jleroux
Date: Sat Sep 22 05:50:10 2007
New Revision: 578422
URL: http://svn.apache.org/viewvc?rev=578422&view=rev
Log:
Applied fix from trunk for revision: 577097
Modified:
ofbiz/branches/release4.0/framework/service/servicedef/services.xml
Modified: ofbiz/branches/release4.0/framework/service/servicedef/services.xml
URL:
http://svn.apache.org/viewvc/ofbiz/branches/release4.0/framework/service/servicedef/services.xml?rev=578422&r1=578421&r2=578422&view=diff
==============================================================================
--- ofbiz/branches/release4.0/framework/service/servicedef/services.xml
(original)
+++ ofbiz/branches/release4.0/framework/service/servicedef/services.xml Sat Sep
22 05:50:10 2007
@@ -26,7 +26,7 @@
<!-- Service Engine Services -->
<service name="purgeOldJobs" engine="java"
- location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true"
use-transaction="false">
+ location="org.ofbiz.service.ServiceUtil" invoke="purgeOldJobs" auth="true"
use-transaction="false" semaphore="wait">
<description>Cleans out old jobs which have been around longer then
what is defined in serviceengine.xml</description>
<required-permissions join-type="AND">
<check-permission permission="SERVICE_INVOKE_ANY"/>
