Spring boot initialization should fail if activity names (per worker) are duplicated

[antmendoza]

Expected Behavior

When registering duplicated activity names in "normal" workers, the worker initialization fail with

"xyz" activity type is already registered with the worker

Users expect the same when they use Spring Boot.

Spring Boot does not fail, it currently prints

Skipping auto-discovered activity bean 'xyzImpl' of class class abc on a worker with a task queue 'taskqueueName123' as activity type 'activityWithNameX' is already registered on the worker

I think the worker initialization should fail

Actual Behavior

Steps to Reproduce the Problem

Specifications

• Version:
• Platform:

[dspitzer]

This bit us as well and can lead to dangerous behavior.