mattrpav commented on PR #949: URL: https://github.com/apache/activemq/pull/949#issuecomment-1374104344
Yeah, I just can't get there with the current approach. I think this could all be handled within the JobScheduler/JobSchedulerFacade and not have to bubble it all the way up to BrokerService. I'd vote -1 for this change as-is. Pinging @cshannon to see if he has any add'l thoughts. My suggested approaches: 1. Extend current JobListener 2. Extend advisory support to send an advisory message w/ the job id, message id and target destination (this would be add add'l broker filter methods, and then support in the AdvisoryBroker so it can be turned off when advisory support is disabled) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
