| Author |
Message
|
| Partha.Baidya |
 Posted: Tue Apr 03, 2018 4:06 pm Post subject: How to maintain multiple versions of shared library |
 |
|
Voyager
Joined: 05 Nov 2009
Posts: 97
|
I came to a situation wherein I kept a WSDL in a shared library. Now the code has been deployed in Production, now I changed some XSD elements and code has to be deployed in UAT.
But how do I maintain different versions of shared library. As library is directly referenced in Application's project file, I can not change the library name.
Could you let me know how is it possible to manintain different version of a shared library? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Apr 03, 2018 8:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Very, very easy.
I am sure that you have the library in source control... So just invoke the correct version from source control... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| timber |
| Posted: Wed Apr 04, 2018 2:53 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1280
|
You can only deploy one version of a shared library into each integration server. That version will be used by all applications in the same integration server.
If you want different applications (in the same integration server) to use different versions of the WSDL then you should put the WSDL into a static library. |
|
| Back to top |
|
|
| Partha.Baidya |
| Posted: Wed Apr 04, 2018 6:01 am Post subject: |
|
|
Voyager
Joined: 05 Nov 2009
Posts: 97
|
| Even if I want to keep different versions in source control, that is not possible. My concern is how name resolution will happen. |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Thu Apr 05, 2018 12:11 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
| Partha.Baidya wrote: |
| Even if I want to keep different versions in source control, that is not possible. My concern is how name resolution will happen. |
Why not? try exploring the 'branching of code' concept, you could have trunk always representing the Prod code level and code from different branches getting deployed to Dev/Test environments. |
|
| Back to top |
|
|
|
|
