Superclassing workflow definition interface causes "process workflow type is already registered with the worker"

[Gromofiz]

Hi :-)

I'm trying to build a generic way for starting workflows.
The idea is to have a common interface (EcmWorkflow) that defines all common methods, ie:

public interface EcmWorkflow {

    @WorkflowMethod()
    void process(Map<String, Object> params);
    ...	    
}

and then extends it with the "real" workflows, for example

public interface TestWorkflow extends EcmWorkflow {
    
    @SignalMethod
    void goNextStatus(Map<String, Object> param);

    @SignalMethod
    void exit();

    @QueryMethod
    OrderStatus getStatus();
}

and

public class TestWorkflowImpl implements TestWorkflow {
   ...
}

When i try to build the worker with

Worker worker = factory.newWorker(TASK_LIST);
worker.registerWorkflowImplementationTypes(TestWorkflowImpl.class);
worker.registerActivitiesImplementations(new TestActivitiesImpl());

the exception

java.lang.IllegalStateException: EcmWorkflow::process workflow type is already registered with the worker

is thrown by

POJOWorkflowImplementationFactory#addWorkflowImplementationType:152

that is called by

worker.registerWorkflowImplementationTypes(TestWorkflowImpl.class);

during worker's creation.

This happens because the TestWorkflowImpl class implements two interfaces, TestWorkflow and EcmWorkflow
both having the same "@WorkflowMethod() process" method, since the first extends the second.
The workflow name, in both cases is, "EcmWorkflow::process" so two @WorkflowMethod() are found when cycling on the implemented interfaces even if there is only one!!

The question: is this a wanted behaviour or a bug?

Enzo