ServiceTask - Parsing and persistence for custom types

christhonie — Wed, 07 Oct 2015 21:13:52 GMT

Dear Activiti team,Thanks for an awesome product! It is clear that years of experience has gone into this.I would like to extend the behavior of a ServiceTask, which I can easily do injecting my own ServiceTaskParseHandler into customDefaultBpmnParseHandlers and providing my own implementation of A

Re: ServiceTask - Parsing and persistence for custom types

jbarrez — Thu, 08 Oct 2015 09:24:01 GMT

Phew … that is a seriously long post. I'm sure I'm missing things when responding to this:

i1. Yes, that is correct from a BPMN spec point of view. However adding those particular attributes won't make it better importable in other products.

i2. That might be correct. Internally it's the WebServiceActivityBehavior that is responsible for the webservice calls. Does it marshal to a servicetask xml with that class?

i3. It sounds right, but I think a PR with actual code makes it easier to discuss and understand what we're talking about. So I'd say yes to getting such a PR read 🙂

Q1. I'm not sure. You say complement, but it will have an impact on existing process definitions, no? Or wat scenario's are you talking about here?

Q2. Not sure what you mean by this. Can you elaborate?

Q3. Same as Q2. I think code would make this a lot easier to understand.

Q4. Yes, the JSON conversion will still matter. The v6 Modeler uses that JSON, so it's not going away anytime soon.

Q5. Yes, if webservice is to be fully supported there is no other solution than storing it in the json too.

Q6. I think the validator simply must become aware of this new kind of service task and change the validation rules there.

Looking forward to discuss further in the PR!

topic Re: ServiceTask - Parsing and persistence for custom types in Alfresco Archive

ServiceTask - Parsing and persistence for custom types

Re: ServiceTask - Parsing and persistence for custom types