Parameterized signal names and event sub-process

[mauro bertapelle]

Following the advices in http://mswiderski.blogspot.it/search/label/jbpm_signal_as_variable , I'm trying to use parameterized signal names in an event sub-process without luck.

I'm using jbpm-6.4.0.Final with wildfly-8.2.1.Final

This is a simple process to reproduce the problem:

The process start and throw a signal whose name is the expression: '#{mySignal}' :

The signal should be catched by an event subprocess, whose start event is configured in the same way:

Then I start the process in this way:

params.put("mySignal", "#{Signal_A}");
ProcessInstance processInstance = client.startProcess(workflowId, params);

And the signal is not received. It seems that variable expressions are not supported inside an event subprocess.

As a countercheck, if I set mySignal value to '#{mySignal}', everything works fine:

params.put("mySignal", "#{mySignal}");
ProcessInstance processInstance = client.startProcess(workflowId, params);

Is this a feature, a bug, or have I misunderstood something ? Any suggestion would be greatly appreciated.

[Maciej Swiderski]

that’s indeed not supported at the moment as event subprocess nodes are instantiated on demand where the requirement is that the name of the signal must match the one defined on it - though it does not resolve variables. I believe it’s a valid feature request so please go ahead and file jira

Maciej

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/c40bd626-c5e1-4982-b8b7-40d632227d82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.