| Author |
Message
|
| Frik |
 Posted: Thu Nov 07, 2013 5:03 am Post subject: A way to hold multiple versions of flow/MessageSet? |
 |
|
Acolyte
Joined: 25 Nov 2009
Posts: 69
|
Hello,
need your help -
There is a requirement in the organization to have multiple versions of a service in the WMB.
I guess that's mean another flow with a different name,
and in case there a difference of aMessageSet in the versions,
there is a need to another message set, with a different name...
Quite hard to maintain!
(That's in case we don't want another ExecutionGroup)
Is there another solutions?
Maybe a best practice to use multiple versions in the broker? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Nov 07, 2013 6:28 am Post subject: Re: A way to hold multiple versions of flow/MessageSet? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Frik wrote: |
| Maybe a best practice to use multiple versions in the broker? |
If you have multiple version of the same service, why isn't version n+1 of the service backwards compatible with version n?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 07, 2013 7:47 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you looked at using a different broker schema if the 2 version have some incompatibility? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dogorsy |
| Posted: Thu Nov 07, 2013 9:02 am Post subject: Re: A way to hold multiple versions of flow/MessageSet? |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
| Frik wrote: |
| I guess that's mean |
You do not make decisions on that. Go and clarify the requirements first. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 07, 2013 9:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You haven't thought throw the whole process of what it means to have "more than one version " of the same service.
There's a lot to be considered, across the entire software development lifecycle. |
|
| Back to top |
|
|
|
|
