Fluent programming on Commands

[camunda]

In jbpm 3 I introduced some "fluent" programming capabilities on Commands, so that you can write:

commandService.execute(
 new StartProcessInstanceCmd()
 .processDefinitionId(5)
 .addVariable("x", 5)
 .executionKey("88"));

What do you think, can we introduce that again? Was very handy for coding!

Shall we again have an extra method for it or just let the setters return the object itself (which would be possible if we do it before the first release I guess)?

[camunda]

Would introduce an empty constructor as well by the way.

And maybe I find the time to add API doc again too :-) But don't want to promise yet...

[camunda]

Yeah, I would definitly like to introduce some API doc. Since providing null for the required parameter as executionKey to have the key generated is not 100% intuitive ;-)

But that would be even a bit easier with the fluent stuff... Or was it called liquid programming? Forgot...

[camunda]

Any opinions on that?

[tom.baeyens]

i don't think commands should be exposed in the api. only the methods in the service interfaces.

in that case the fluentness of the comand api becomes an internal impl detail.

ok with the fluent api. but don't see the need to spend time on it as it's an impl detail.