cshannon opened a new pull request, #2075: URL: https://github.com/apache/activemq/pull/2075
**Note:** This change adds a new method to the Broker API. Most users should be ok if they use the BrokerFilter for plugins (the most common scenario) but it's possible this could be a breaking change, however the update I think is worth it. We can document the change in release notes. This updates the AdvisoryBroker to always publish advisory messages that were generated by other events to use the Broker's own ConnectionContext. Before this change the AdvisoryBroker was using the original ConnectionContext that used used for the action that triggered the advisory. This doesn't make sense because its actually the broker itself firing the advisory message and not the original connection. It also meant requiring all users to be given access to create new advisory topics that could be created on demand. After this update, all users no longer need permission to create advisory destinations which was required previously. Users only need read access to the temporary destination advisories for the AMQ client as the broker itself will now use its own context going forward to create all the destinations on demand and for publishing. This update also consolidates the on consumer with no messages advisory into the Advisory broker so it is all managed in one location. (cherry picked from commit 3598fc562337c467b3f6b59364b29ac2d9bdb068) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
