Administrator
|
Hi,
We still have the default-no-eca delegator definition in entityengine.xml I believe it was used when OFBiz was still using a workflow engine (Shark was the last). I don't see any needs now, but maybe by Hans with Activiti. So my question: should we get rid of it? Else we should simply document it in entityengine.xml with the other delegator (a simple sentence) Thanks Jacques |
We use this definition when we create a service that manage many data
for massive import for performance or escape functional case. I'm in favor to keep it, or if we rip maybe set it to comment with an example to how use it Nicolas Le 04/10/2017 à 10:21, Jacques Le Roux a écrit : > Hi, > > We still have the default-no-eca delegator definition in entityengine.xml > > I believe it was used when OFBiz was still using a workflow engine > (Shark was the last). I don't see any needs now, but maybe by Hans > with Activiti. > > So my question: should we get rid of it? Else we should simply > document it in entityengine.xml with the other delegator (a simple > sentence) > > Thanks > > Jacques > > |
Administrator
|
Thanks Nicolas,
Then I suggest to keep it and document where it's used (in entityengine.xm) with a simple sentence What would you suggest, maybe simply using the example you gave? Jacques Le 04/10/2017 à 16:53, Nicolas Malin a écrit : > We use this definition when we create a service that manage many data for massive import for performance or escape functional case. > > I'm in favor to keep it, or if we rip maybe set it to comment with an example to how use it > > Nicolas > > > Le 04/10/2017 à 10:21, Jacques Le Roux a écrit : >> Hi, >> >> We still have the default-no-eca delegator definition in entityengine.xml >> >> I believe it was used when OFBiz was still using a workflow engine (Shark was the last). I don't see any needs now, but maybe by Hans with Activiti. >> >> So my question: should we get rid of it? Else we should simply document it in entityengine.xml with the other delegator (a simple sentence) >> >> Thanks >> >> Jacques >> >> > > |
Administrator
|
Done at r1811571
Jacques Le 04/10/2017 à 17:30, Jacques Le Roux a écrit : > Thanks Nicolas, > > Then I suggest to keep it and document where it's used (in entityengine.xm) with a simple sentence > > What would you suggest, maybe simply using the example you gave? > > Jacques > > > Le 04/10/2017 à 16:53, Nicolas Malin a écrit : >> We use this definition when we create a service that manage many data for massive import for performance or escape functional case. >> >> I'm in favor to keep it, or if we rip maybe set it to comment with an example to how use it >> >> Nicolas >> >> >> Le 04/10/2017 à 10:21, Jacques Le Roux a écrit : >>> Hi, >>> >>> We still have the default-no-eca delegator definition in entityengine.xml >>> >>> I believe it was used when OFBiz was still using a workflow engine (Shark was the last). I don't see any needs now, but maybe by Hans with Activiti. >>> >>> So my question: should we get rid of it? Else we should simply document it in entityengine.xml with the other delegator (a simple sentence) >>> >>> Thanks >>> >>> Jacques >>> >>> >> >> > |
Thanks Jacques, I appreciate :)
Nicolas Le 09/10/2017 à 19:05, Jacques Le Roux a écrit : > Done at r1811571 > > Jacques > > > Le 04/10/2017 à 17:30, Jacques Le Roux a écrit : >> Thanks Nicolas, >> >> Then I suggest to keep it and document where it's used (in >> entityengine.xm) with a simple sentence >> >> What would you suggest, maybe simply using the example you gave? >> >> Jacques >> >> >> Le 04/10/2017 à 16:53, Nicolas Malin a écrit : >>> We use this definition when we create a service that manage many >>> data for massive import for performance or escape functional case. >>> >>> I'm in favor to keep it, or if we rip maybe set it to comment with >>> an example to how use it >>> >>> Nicolas >>> >>> >>> Le 04/10/2017 à 10:21, Jacques Le Roux a écrit : >>>> Hi, >>>> >>>> We still have the default-no-eca delegator definition in >>>> entityengine.xml >>>> >>>> I believe it was used when OFBiz was still using a workflow engine >>>> (Shark was the last). I don't see any needs now, but maybe by Hans >>>> with Activiti. >>>> >>>> So my question: should we get rid of it? Else we should simply >>>> document it in entityengine.xml with the other delegator (a simple >>>> sentence) >>>> >>>> Thanks >>>> >>>> Jacques >>>> >>>> >>> >>> >> > > |
Free forum by Nabble | Edit this page |