(is this the correct forum? I'd say "no", because actions are not necessarily related to the webclient, but I didn't find any forum that seemed better suited to me)
Can a custom action, in its executeImpl, call a different [custom] action?
I'd say "no", as i tried and the second executeImpl deadlocks on getParameterValue… in that case: what's the suggested way to do it?
Of course, both custom actions being written by me, I can always refactor one to expose a method that does most of the job of the "inner" action, so that the outer one can call that instead of invoking the action itself, but I wonder if a different approach could work/be-better.