JavaDelegates, custom nodes, configuration and use

msandoz — Sat, 17 Dec 2011 15:39:35 GMT

I read this: Since the Java class instance is reused, the injection only happens once, when the serviceTask is called the first time. When the fields are altered by your code, the values won't be re-injected so you should treat them as immutable and don't make any changes to them.I defined several c

Re: JavaDelegates, custom nodes, configuration and use

msandoz — Mon, 19 Dec 2011 03:39:34 GMT

I've been testing the behavior on 5.8 over the weekend and there seem to be some interesting changes in the delegate behavior.

The delegates now do appear to be instance-specific and can be configured differently, even multiple times within a process.

They now also seem to handle expressions, which can be declared via member properties, and can be evaluated at execution time, even referring to spring variables.

This is very nice!

I was wondering though - I'd like the code I'm actually delegating to - the business logic - to be a spring bean, which is invoked by the delegate. What's the best way from the delegate to get to the engine to be able to resolve beans? I could pass the business logic spring bean in the expressions, but this seems to be counter-intuitive to a user. Is there some way to request an arbitrary bean from what I have available - the DelegateExecution - or should I use some other means?

Also, on the topic of the generation of the bpm20 xmls, it is strange that this code:

FieldExtensionsExport.java

      for (FieldExtension fieldExtension : fieldExtensionList) {
        if(fieldExtension.getFieldname() != null && fieldExtension.getFieldname().length() > 0 &&
                fieldExtension.getExpression() != null && fieldExtension.getExpression().length() > 0) {
          
          xtw.writeStartElement(ACTIVITI_EXTENSIONS_PREFIX, "field", ACTIVITI_EXTENSIONS_NAMESPACE);
          xtw.writeAttribute("name", fieldExtension.getFieldname());
          if (fieldExtension.getExpression().contains("${")) {
            xtw.writeStartElement(ACTIVITI_EXTENSIONS_PREFIX, "expression", ACTIVITI_EXTENSIONS_NAMESPACE);
          } else {
            xtw.writeStartElement(ACTIVITI_EXTENSIONS_PREFIX, "string", ACTIVITI_EXTENSIONS_NAMESPACE);
          }
          xtw.writeCharacters(fieldExtension.getExpression());
          xtw.writeEndElement();
          xtw.writeEndElement();
        }
      }

is not called from ServiceTaskExport, which has the rather less powerful:

    if (serviceTask.getResultVariableName() != null && serviceTask.getResultVariableName().length() > 0) {
      xtw.writeAttribute(ACTIVITI_EXTENSIONS_PREFIX, ACTIVITI_EXTENSIONS_NAMESPACE, "resultVariableName", serviceTask.getResultVariableName());
    }

The difference is that since the custom node editor always creates a servicetask, there is no way to generate variable expressions using the custom nodes. Would it be reasonable for me to add a Jira for an enhancement for this?

Re: JavaDelegates, custom nodes, configuration and use

tiesebarrell — Mon, 19 Dec 2011 08:26:46 GMT

There might be a specific reason for that, but you should certainly file an issue so we can look into it. If you do, please reference this thread so we can lookup the details.

Re: JavaDelegates, custom nodes, configuration and use

msandoz — Mon, 19 Dec 2011 12:09:40 GMT

ACT-1033 - ServiceTaskExport does not take advantage of expressions

for the export issues.

I will start a new thread on the other issue.

topic Re: JavaDelegates, custom nodes, configuration and use in Alfresco Archive

JavaDelegates, custom nodes, configuration and use

Re: JavaDelegates, custom nodes, configuration and use

Re: JavaDelegates, custom nodes, configuration and use

Re: JavaDelegates, custom nodes, configuration and use