topic Re: Programmatic creation of a process and using activiti XSD entries in Alfresco Archive

Programmatic creation of a process and using activiti XSD entries

johnament1 — Tue, 27 May 2014 12:35:09 GMT

Hi all,I'd like to programmatically setup my process flows, for a number of reasons the XML files don't work for what I'm trying to do.I'd like to be able to set the attributes like activiti:expression in my process, however I don't see an appropriate setter in BPMN's ServiceTask to properly point t

Re: Programmatic creation of a process and using activiti XSD entries

johnament1 — Tue, 27 May 2014 13:52:33 GMT

A little more info.

so, digging through your code I found these validation rules: https://github.com/Activiti/Activiti/blob/master/modules/activiti-process-validation/src/main/java/org/activiti/validation/validator/impl/ServiceTaskValidator.java

Which is why I'm getting this: One of the attributes 'class', 'delegateExpression', 'type', 'operation', or 'expression' is mandatory on serviceTask.

In my case, I want to use an expression, but I don't want to use camel or mule; and shell and mail don't fit my purposes either. When I look at the user guide, I see that this is what the XML would look like:

<java>
<serviceTask id='approveOrDissaprove' name='Store decision'
activiti:expression="${loanRequest.setApproved(approvedByManager)}" />
</java>
Which doesn't have a type either.

Re: Programmatic creation of a process and using activiti XSD entries

johnament1 — Tue, 27 May 2014 16:38:46 GMT

I decided to try verifying my problem. I copied the validation logic in to my test class, just to see if it passes.

<java>
        ServiceTask foobar = new ServiceTask();
        foobar.setName("foobar");
        foobar.setId("foobar");
        foobar.setImplementationType(ImplementationType.IMPLEMENTATION_TYPE_EXPRESSION);

        if (!ImplementationType.IMPLEMENTATION_TYPE_CLASS.equalsIgnoreCase(foobar.getImplementationType())
                && !ImplementationType.IMPLEMENTATION_TYPE_DELEGATEEXPRESSION.equalsIgnoreCase(foobar.getImplementationType())
                && !ImplementationType.IMPLEMENTATION_TYPE_EXPRESSION.equalsIgnoreCase(foobar.getImplementationType())
                && !ImplementationType.IMPLEMENTATION_TYPE_WEBSERVICE.equalsIgnoreCase(foobar.getImplementationType())
                && StringUtils.isEmpty(foobar.getType())) {
            System.out.println("Type was "+foobar.getType()+" and impl type was "+foobar.getImplementationType());
        }
        else {
            System.out.println("Not Type was "+foobar.getType()+" and impl type was "+foobar.getImplementationType());
        }
</java>

Turns out that I'm getting in to the "else" block of the code in my case, which doesn't match what is happening in the validator. I'm on activiti 5.15.1. Is it possible that there's a bug?

Re: Programmatic creation of a process and using activiti XSD entries

jbarrez — Fri, 30 May 2014 09:00:14 GMT

If you are working around the defaults of the engine, another route might be simply to disable that specific rule. The validator is pluggable and you can remove rules from the ValidatorSet on the ProcessEngineConfiguratiomImpl.