| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| CDataSection to XML |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Tue Aug 11, 2015 6:57 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sleepyjamie wrote: |
| I do use trace nodes for capturing errors/exceptions, |
Interesting use case. Why those, rather than more obvious means?
| sleepyjamie wrote: |
| however for generic tracing between nodes I try to avoid them because they often make a mess of the flow. |
No more than any other node, and I value the function of my flows over their artistic merit.
(If the next guy to make a change wants to use that everything-at-right-angles thing, more power to him).
Note that it's possible to switch Trace nodes on and off administratively. While they should be off in Prod routinely, it's amazing how much debugging time you can save switching them on while a problem use case goes through.
| sleepyjamie wrote: |
| It would be nice if IIB had a way to enable tracing at the input and output of a node without having to physically drop a trace node onto the palette. |
Write that here, and be sure to post the resulting link in a thread for us. You'll get my vote. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Aug 11, 2015 6:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| sleepyjamie wrote: |
| It would be nice if IIB had a way to enable tracing at the input and output of a node without having to physically drop a trace node onto the palette. |
You mean a monitoring profile that controls event monitoring that acts at a node or terminal level?
That can be used with record/replay?
Like that? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 11, 2015 7:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| sleepyjamie wrote: |
| It would be nice if IIB had a way to enable tracing at the input and output of a node without having to physically drop a trace node onto the palette. |
You mean a monitoring profile that controls event monitoring that acts at a node or terminal level?
That can be used with record/replay?
Like that? |
That's certainly where my head was at, except it writes to the user trace rather than out as an event.
And yes, I know you can do the same sort of thing with the existing functionality and a little dancing. I've done it myself. But I think it would be a useful addition to have a shrink-wrapped debugging profile separate & independent to the monitoring profile.
So I'd vote for the RFE.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sleepyjamie |
| Posted: Tue Aug 11, 2015 7:09 am Post subject: |
|
|
Centurion
Joined: 29 Apr 2015
Posts: 135
|
| mqjeff wrote: |
| sleepyjamie wrote: |
| It would be nice if IIB had a way to enable tracing at the input and output of a node without having to physically drop a trace node onto the palette. |
You mean a monitoring profile that controls event monitoring that acts at a node or terminal level?
That can be used with record/replay?
Like that? |
Sort of yes. I don't really need monitoring at an ops level. Enabling monitoring events seems like overkill for what I need. I will check out the record/reply but that feature seems very heavy for what I want to do.
What I would like is a simple input/output trace log that I can apply to a node without having to draw Trace Nodes into my flows. If record/replay provides this then great. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Wed Aug 12, 2015 10:33 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
| sleepyjamie wrote: |
I just realized in my SOAPUI that the response is returning a CData nested inside another CData, which contains a sibling CData. So I have a feeling this is also causing issues in IIB.
 |
Or any XML parser. I've seen "nested" CDATA before but it has to be setup very carefully since you can't have multiple ]]> within one CDATA. It basically has to be multiple CDATA sections one after another with the end tag split between neighboring CDATA elements. Quite a pain. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
