| Author |
Message
|
| udaya_isampalli |
 Posted: Mon Aug 20, 2007 1:50 am Post subject: Issue with '&' while creating XML Output |
 |
|
Novice
Joined: 09 Feb 2007
Posts: 13
|
Hi,
We have requirement where input is Fixed width message and output is XML message with (XML Domain). When input fields contain "&" the MB Should by default need to convert to "&". But it was not doing so.
In the output also it is coming like just "&" so while opening in explorer it is giving problem.
Do we need to do any extra configuration?
thank you
regards
Uday |
|
| Back to top |
|
 |
| asudhakar |
| Posted: Mon Aug 20, 2007 2:05 am Post subject: Re: Issue with '&' while creating XML Output |
|
|
Centurion
Joined: 12 May 2007
Posts: 116
Location: Bangalore
|
| uday_MCA wrote: |
Hi,
We have requirement where input is Fixed width message and output is XML message with (XML Domain). When input fields contain "&" the MB Should by default need to convert to "&". But it was not doing so.
In the output also it is coming like just "&" so while opening in explorer it is giving problem.
Do we need to do any extra configuration?
thank you
regards
Uday |
Input message is Fixed width so its better to mention TDS format.
If we create a message definition file which supports TDS AND XML we can solve above prob.
But, we need to mention MRM domain. by Reset content descriptor node we can change parser.
just try it. |
|
| Back to top |
|
|
| udaya_isampalli |
| Posted: Mon Aug 20, 2007 2:41 am Post subject: |
|
|
Novice
Joined: 09 Feb 2007
Posts: 13
|
Hi Sudhakar,
In the same interface we have another flow which is taking TDS input and producing the XML output, But there when input contains the '&' with input in MRM domain and output is to XML with XML domain is getting "&" but from CWF to XML we are not getting.
Uday |
|
| Back to top |
|
|
| asudhakar |
| Posted: Mon Aug 20, 2007 3:01 am Post subject: |
|
|
Centurion
Joined: 12 May 2007
Posts: 116
Location: Bangalore
|
| uday_MCA wrote: |
Hi Sudhakar,
In the same interface we have another flow which is taking TDS input and producing the XML output, But there when input contains the '&' with input in MRM domain and output is to XML with XML domain is getting "&" but from CWF to XML we are not getting.
Uday |
Yes Uday.
Then the problem solved. if he want to change the parser at middle of the message flow then he should be use Reset content descriptor node.
_________________
WebSphere MQ, MB Support and Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Aug 20, 2007 3:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Please don't use the XML Domain.
Use XMLNS or XMLNSC.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Aug 20, 2007 3:56 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| In the same interface we have another flow which is taking TDS input and producing the XML output, But there when input contains the '&' with input in MRM domain and output is to XML with XML domain is getting "&" but from CWF to XML we are not getting. |
The output message written by the XML domain is controlled by the contents of the message tree which the output node sees. The output is not affected by the input parser ( CWF / TDS ).
If you want to find out why one message flow is not performing the substitution, put a Trace node before the output node and compare the results.
The XML parser ( and the XMLNS / XMLNSC parsers ) will replace & with & wherever they occur - regardless of whether TDS/CWF was used earlier in the flow. |
|
| Back to top |
|
|
|
|
