topic Allowing expressions in properties of CustomServiceTask in Alfresco Archive

Allowing expressions in properties of CustomServiceTask

f3lix — Fri, 15 Jul 2011 09:46:49 GMT

Hello,I followed the user guide and successfully added and entry to the designer's palette by extending AbstractCustomServiceTask and adding the appropiate annotations.If i have a text property like this:@Property(type = PropertyType.TEXT, displayName = "Service endpoint URL")private String endpoint

Re: Allowing expressions in properties of CustomServiceTask

tiesebarrell — Fri, 15 Jul 2011 10:12:55 GMT

Good point. This is something we should support. As a start we could detect whether you entered a string that is probably meant as an expression and generate the other item instead - I'm not sure whether we can effectively catch other scenarios with mixed strings like "ms ${piggy} went to town". One thing I'll need to check is whether the injection in the runtime class needs adjustment or not. Can you please create a Jira issue that references this thread and assign it to me (Tiese Barrell)? Then I'll make sure it makes its way into Designer. Thanks.

Re: Allowing expressions in properties of CustomServiceTask

f3lix — Fri, 15 Jul 2011 10:29:50 GMT

Thanks for your fast response.

I created a ticket (http://jira.codehaus.org/browse/ACT-877) but could not assign it to you.

Felix

Re: Allowing expressions in properties of CustomServiceTask

tiesebarrell — Fri, 15 Jul 2011 10:39:56 GMT

Great, thanks. I forgot you can't assign it directly. I claimed the issue.

Re: Allowing expressions in properties of CustomServiceTask

f3lix — Fri, 15 Jul 2011 12:11:24 GMT

For now I created a workaround by evaluating the expression within the JavaDelegate, so <activiti:string> will also be evaluated as expression.


public class QueryDelegate implements JavaDelegate

 Expression query;
 Expression endpointURL;

 @Override
 public void execute (DelegateExecution execution) throws Exception
 {
  ExpressionFactory ef = new ExpressionFactoryImpl ();
  ELContext context = new ActivitiElContext (new VariableScopeElResolver (execution));
  
                // instead of: String queryString = (String)query.getValue (execution); 
  ValueExpression ex = ef.createValueExpression (context, query.getExpressionText (), String.class);
  String queryString = (String) ex.getValue (context); 
             
               // instead of: String endpointUrlString = (String)endpointURL.getValue(execution);                       
  ex = ef.createValueExpression (context, endpointURL.getExpressionText (), String.class);
  String endpointUrlString = (String) ex.getValue (context); 

              … 
        }
}

I am not sure if this will break something, but it seems to work …

Regards,
Felix