| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Making a single bar file containing all the subflows |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sonal |
 Posted: Wed Nov 03, 2010 9:53 am Post subject: Making a single bar file containing all the subflows |
 |
|
Apprentice
Joined: 20 Mar 2009
Posts: 45
|
Hi Experts,
I've few subflows that are being used in almost all the message flows we've in our system. Now, I want to build a bar file that contains all the sub-flows. The reasons why I want to do it are:
Firstly, I dont need to put all the subflows in project reference everytime for every message flow. Instead just keep that bar file in project reference.
Secondly, in current scenario, any change made in one sub-flow would mean change in all the message flows that are using that particular subflow. Now the idea is, if I'll have one bar file having all the subflows in it n if I could put that bar file in project reference... then any change made in subflow would mean to change n redeploy just one bar file rather than changing and deploying all the message flows once again.
Now my question is, is it possible to do so? Especially when we cannot add independent subflow in bar file? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 03, 2010 10:08 am Post subject: Re: Making a single bar file containing all the subflows |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sonal wrote: |
| Now my question is, is it possible to do so? |
No. Because...
| Sonal wrote: |
| Especially when we cannot add independent subflow in bar file? |
Also
| Sonal wrote: |
| if I could put that bar file in project reference |
You can't do this either.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 03, 2010 10:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
3 methods I've seen used to manage your scenario:
1) Break the subflows out & call them with SOAP, WMQ, etc
2) Set up your source code control to manage the rebuilding & redeployment of the containing flows on change of sub flow
3) Apply standards to the changing of the sub flows so a) it doesn't happen or b) the new sub flow is backwards compatible
Other solutions are undoubtably possible, no method listed here is recommended over any other & no implication is made that they are applicaible to your particular situation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
