| Author |
Message
|
| deeps1281 |
 Posted: Tue Nov 06, 2007 11:02 pm Post subject: Common project reference in same execution group |
 |
|
Apprentice
Joined: 31 Aug 2005
Posts: 29
|
A very basic question.
If i have 2 flows deployed in a execution group using the same common code in the project reference.If I update the common code and redeploy one of the flows in the same execution group would my second flow start using the updated common code or the one with which it was deployed initially.
I have tested it and it shows that the second flow keeps using the common code with which it was deployed and not the updated one.But I need to provide a reference where it is documented.
Can anyone provide me any pdf reference where such behaviour is written down.
Thanks in advance |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Nov 06, 2007 11:14 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi deeps1281,
Instead of then looking at the MB documentation you should look at some Java/JVM docs, where they talk about compilations and threads not getting automatically updated with updates in code...
Regards. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Nov 06, 2007 11:44 pm Post subject: Re: Common project reference in same execution group |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| deeps1281 wrote: |
If i have 2 flows deployed in a execution group using the same common code in the project reference.If I update the common code and redeploy one of the flows in the same execution group would my second flow start using the updated common code or the one with which it was deployed initially.
Can anyone provide me any pdf reference where such behaviour is written down.
|
your observations are in sync with my understanding of MB 
copied from infocenter
A BAR file is a standard ZIP file with the extension .bar instead of .zip. It is similar to the EAR files used for J2EE deployment packaging, which are ZIP files with the extension .ear instead of .zip.
A BAR file contains a single deployment descriptor, known as broker.xml, along with compiled message flows, message set dictionaries, XML, XSLT, and JAR files used by the Java compute node or within ESQL code.
hence the change in flow was compiled and put in next bar file and not the one already deployed....
_________________
Cheers |
|
| Back to top |
|
|
| deeps1281 |
| Posted: Wed Nov 07, 2007 1:02 am Post subject: Re: Common project reference in same execution group |
|
|
Apprentice
Joined: 31 Aug 2005
Posts: 29
|
Appreciate your help on this ,but the problem is that our client wants some sort of documentation stating that this is the behaviour of the broker.
Let me see what I can find on this |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 07, 2007 3:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Remember as well that subflows are really compiled and packaged with the mainflow.
So a change to a common subflow will not affect any other flow but the ones you compiled and deployed after the change...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
