Activiti | Create a generic Service task to send XML Over HTTP -

as continued part of our activiti evaluation doing poc migrate our existing templates bpmn specs. need migrate existing tasks , 1 of critical task communicate mother application using xml on http. planning create service task (java delegate) purpose. task has reusable can use in different process definitions , in same definition different invocation within same definition. achieve this, service task needs provided initialization parameters xml body. initialization parameters include:

url of mother application authentication credentials 

my query , confusion how best implement requirement.

for example, can keep initialization parameters in properties file , create sub process own service task read file. sub process part of main process. alternatively, can read properties file in service task, instead of creating sub process

what best practice/guideline type of scenario. 

the xml body (means content of xml) vary per process definitions , need parametrized. best way provide xml service task, given fact reusable task. example, shall define xml part of .bpmn.xml file or should create separate template files identifier , use them in service task(the 1 send xml on http) thanks

we using activiti bpmn heavily in our products , never thought feeding xml bpmn file. generate xml files on fly of service tasks. in case don't worry bpmn files, update generation mechanism , xml file generated without touching deployed process definitions.

this generation mechanism externalized source code, use velocity templates , processes gives required parameters service task can decide template use.

our cases seems alike, use 1 service task each request, passes parameters template according other parameters.