begin-end or start-stop

[tom.baeyens]

currently the names of the ClientProcessDefinition are not yet in sync with the ExecutionService

ClientProcessDefinition has a beginProcessInstance method because ClientExecution has an method end.

We could rename the ExecutionService start methods to begin.

But instead we could also use the start-stop naming scheme and implement that consistently.

At this point, that feels better to me, but maybe there was a reason why i choose execution.end in the first place...

WDYT ?

[kukeltje]

funny... lots of responses on the businesskey thing, none here... maybe nobody really cares, has an opinion (on this issue)... ok now my €0.014

begin-end: used to that from jBPM 3,
start-stop: nothing wrong with this either

But... and now comes the funny part, I was going to say, why not start-end or begin-stop, initially as a joke. Then, in the light of the BPMN discussion, I was just curious what other 'specs' use and to my surprise, BPMN has a start event and and end event... No my 'joke' is suddenly not funny anymore (ok, it wasn't funny in the first place either ;-) )

long story short... I'm lost and have no preference at all. Take your pick

[tom.baeyens]

i'm choosing the start-stop combination

[kukeltje]

ok fine, but do have one little remark that just came up. Something you stop, can often be (re) started again (like a stopwatch). So that might give a little confusion. Something that has ended (like a footballmatch) cannot be restarted. It can be suspended/resumed, and that is to me more in line with a begin-end... so....