| Author |
Message
|
| jsware |
 Posted: Fri Mar 06, 2015 9:47 am Post subject: Subflows in msgflows warning |
 |
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
We have quite a big Message Broker estate with lots of application built over time on V8.0 of WMB.
I have just applied v8.0.0.2 to my toolkit and now, every msgflow that contains input/Output nodes (ie its really a subflow but we haven't got round to converting them all yet) generates a warning for each copy of the Input/Output node:
| Quote: |
| Subflow defined in the com/.../MainFlowName.msgflow file within message flow is supported during development but handled differently when added to the BAR file. When deployed, it can only be in-lined into the parent flow as part of compiled flow CMF. If you choose to deploy the parent flow as a source file then the error message is displayed during creation of the BAR file. |
and every main flow that uses a subflow gets a warning for each use of the subflow:
| Quote: |
| Subflow defined in the com/.../MsgFlowName.msgflow file within message flow is supported during development but handled differently when added to the BAR file. When deployed, it can only be in-lined into the parent flow as part of compiled flow CMF. If you choose to deploy the parent flow as a source file then the error message is displayed during creation of the BAR file. |
This generates lots of warning (like 82 for just one project and I have like 100+ projects). I know that eventually we'd migrate, but thats not just a quick fix. I know the limitation that we cannot deploy these old-style subflows as separate artifacts and that they get inlined into the main flow - that's fine for now.
What I wondered is if there's a way of supressing this warning so I can see the real warnings from these notices?
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Mar 06, 2015 12:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you tried configuring your problem view for content? (See menu drop down from right hand side icons)
What happens then? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jsware |
| Posted: Fri Mar 06, 2015 2:05 pm Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| fjb_saper wrote: |
Have you tried configuring your problem view for content? (See menu drop down from right hand side icons)
What happens then? |
Ahah - I was right clicking on the warnings to see if a filter option came up and looking in the preferences for warning settings. I'll check the RHS icons for a dropdown 
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| jsware |
| Posted: Wed Mar 18, 2015 12:38 pm Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
Hmm,
Further to my post, I can configure a problems view for all entries that do not contain the specified text - so I can choose the boilerplate text in&around my flow names etc.
However, since I get two separate types of messages, I can only eliminate one of them (the filtering can have multiple text entries to filter out as far as I can tell).
Close but frustratingly far...
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 19, 2015 4:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What you want to filter on is not so much the content than the scope.
Make sure you only get the information for the current (highlighted) element and its children.
Especially when working on a conversion project it allows you to focus getting rid of all the errors in a file - or a project - without getting distracted by the errors still present in the workspace. Conquer one at a time.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
