Before

• @EnableExternalTaskSubscriptions
  • Behavior
    • External Task Client bean is bootstrapped, and handler beans with @ExternalTaskSubscription are automatically picked-up and subscribed in the External Task Client
    • When baseUrl is empty, External Task Client is not bootstrapped
    • Implicitly/automatically used in spring boot starter; no need to specify it (mandatory in the spring-only implementation)
• @DisableDefaultExternalTaskRegistration
  • Behavior: When combined with @EnableExternalTaskSubscriptions, handler beans with a @ExternalTaskSubscription annotation are not automatically picked-up
  • Annotation is used internally in the spring boot module in combination with the @EnableExternalTaskSubscriptions({baseurl = ""}) annotation on CamundaBpmClientAutoConfiguration; However, I don't see a technical reason for it since the absence of @EnableExternalTaskSubscriptions is technically the same
  • I don't see any use case in which a user wants to disable the behavior to pick-up handler beans annotated with @ExternalTaskSubscription except the usage mentioned above, which, as described above, makes no sense
• @ExternalTaskSubscription
  • Behavior: Assign a handler bean to a subscription

Now

• @EnableExternalTaskSubscriptions renamed to @EnableExternalTaskClient
• @DisableDefaultExternalTaskRegistration removed since the use case is unclear; it might be reintroduced if we receive user feedback
• @EnableExternalTaskClient
  • Implicitly/automatically used in spring boot starter; no need to specify it (mandatory in the spring-only implementation)
    • The default External Task Client bean is always created unless the user exposes a custom External Task Client bean in the spring boot application which leads to skipping the creation of the default External Task Client bean
  • External Task Client is tried to be also bootstrapped with baseUrl = "" but bootstrapping fails in this case (exception is thrown by the external task client)