SpringCloud/spring-cloud-bus
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

treat the 'destination' param as path while match using a PathMatcher

Browse Source 
Specifically an AntPathMatcher with the separator as a colon (:)

fixes gh-17
This commit is contained in:
Spencer Gibb
2015-04-08 13:43:37 -06:00
parent 9593414c27
commit ca7aa9a49c
4 changed files with 92 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/src/main/asciidoc/spring-cloud-bus.adoc
View File

@@ -16,6 +16,10 @@ include::quickstart.adoc[]
The HTTP endpoints accept a "destination" parameter, e.g. "/bus/refresh?destination=customers:9000", where the destination is an `ApplicationContext` ID. If the ID is owned by an instance on the Bus then it will process the message and all other instances will ignore it. Spring Boot sets the ID for you in the `ContextIdApplicationContextInitializer` to a combination of the `spring.application.name`, active profiles and `server.port` by default.
== Addressing all instances of a service
The "destination" parameter is used in a Spring `PathMatcher` (with the path separator as a colon `:`) to determine if an instance will process the message. Using the example from above, "/bus/refresh?destination=customers:**" will target all instances of the "customers" service regardless of the profiles and ports set as the `ApplicationContext` ID.
== Customizing the AMQP ConnectionFactory
If you are using AMQP there needs to be a `ConnectionFactory` (from