-
1. Re: Versioning of services with divert
jbertram Dec 17, 2014 1:42 PM (in response to werrenmi)So you have a divert whose <address> and <forwarding-address> are the same? I wouldn't expect that configuration to function properly as messages will be diverted endlessly. What's the intended goal of such a configuration?
-
2. Re: Versioning of services with divert
werrenmi Jan 9, 2015 9:51 AM (in response to jbertram)Hi Justin
Sorry for my very late answer. We want to solve the versioning of our consumers via filters. One solution is to replace the producers also when a new version of a consumer comes in action. But this results in maybe unnecessary deployments of modules they contains the producers. So we target a way to update / define the version in message properties on an central point. Here i played around with diverts, but i have noticed that the transformer will only be invoked when the filter condition on the divert configuration is true for a message (different forwarding-address),
I don't found a further way to solve this. We use the core api.
Regards
Michel
-
3. Re: Versioning of services with divert
jbertram Jan 9, 2015 3:52 PM (in response to werrenmi)Take a look at remoting interceptors. They can intercept and transform messages in arbitrary ways.
-
4. Re: Versioning of services with divert
werrenmi Jan 13, 2015 1:06 AM (in response to jbertram)Thanks a lot Justin! With the remote interceptors it works perfectly.
Regards
Michel