[
https://issues.apache.org/jira/browse/ARTEMIS-4510?focusedWorklogId=910083&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910083
]
ASF GitHub Bot logged work on ARTEMIS-4510:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Mar/24 10:45
Start Date: 15/Mar/24 10:45
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4681:
URL:
https://github.com/apache/activemq-artemis/pull/4681#issuecomment-1999392303
@clebertsuconic @jbertram Let me know if you want me to either:
Remove the condition and new address setting for auto-creation and simply
auto create if the destination is configured for it
Or to add a subscribe to changes by registering a listener on the
HierarchicalRepositoryChangeListener.
I can go either way but personally I prefer the first option... the risk of
breaking a preexisting use-case where sending directly to a non existing
destination should create it but diverting to it should silently fail seems
small... perhaps a note about this change of semantics could be added to the
versions doc instead?
Issue Time Tracking
-------------------
Worklog Id: (was: 910083)
Time Spent: 3h 20m (was: 3h 10m)
> Add auto-create-destination logic to diverts
> --------------------------------------------
>
> Key: ARTEMIS-4510
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4510
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> This enables the use of dynamic routing decisions within the transformer by
> setting the message address. It also covers for a rare problem where if any
> of the forwarding addresses are removed during runtime, such as from
> auto-delete, the message would get silently dropped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
