| Author |
Message
|
| SandiSan |
 Posted: Mon Apr 14, 2008 10:52 pm Post subject: Fix Pack 6.0.0.7 Issue |
 |
|
Acolyte
Joined: 01 Apr 2006
Posts: 57
Location: Pune/India
|
Hi,
Recently i have applied message broker Fix Pack 6.0.0.7. After applying the fix pack i am facing a strange problem.
Broker is removing empty element for e.g. <name/> from the input xml message.I have tried with XMLNSC ,XMLNS and XML parser option in MQInput node but the issue remains.
Before applying the fix pack there was no such issue.
I wonder is anyone else faced the same issue after applying the fix pack.
Regards
Sandisan |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Apr 15, 2008 12:25 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Please be more specific. Does this happen to all empty tags, or just one tag in one of your messages?
Please post example XML and the corresponding Trace node output. |
|
| Back to top |
|
|
| SandiSan |
| Posted: Tue Apr 15, 2008 2:00 am Post subject: |
|
|
Acolyte
Joined: 01 Apr 2006
Posts: 57
Location: Pune/India
|
Thanks for replying kimbert
All empty tags in XML are removed.Attaching sample xml
Sample XML
<Employee>
<NAME>
<FNAME offset = "Added">PK</FNAME>
<MNAME/>
<LNAME></LNAME>
</NAME>
<GENDER/>
</Employee> |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Apr 15, 2008 2:29 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| ...and the corresponding Trace node output |
|
|
| Back to top |
|
|
| smahon |
| Posted: Tue Apr 15, 2008 11:26 am Post subject: |
|
|
Apprentice
Joined: 24 Apr 2002
Posts: 29
|
| Looks like we have this issue as well. Installed FP7 on Friday...reports of missing tags in previously working flows since then. We backed it out and now it is working again. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Apr 16, 2008 4:00 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
SandiSan: Please give more details. Where do you see the empty tags 'removed'. I've tried your XML, and it parses OK on my machine.
smahon: Same request : more details please. Please be very specific about the symptoms ( i.e. where are the tags missing from ). |
|
| Back to top |
|
|
| mlafleur |
| Posted: Fri Apr 18, 2008 1:47 pm Post subject: |
|
|
Acolyte
Joined: 19 Feb 2004
Posts: 73
|
For XMLNSC does 0x00000000 represent anything?
xml tag:
<netcomCustomerInstall customerName="VOIP BUND W/DIG TRUNK JPJ357"/>
fix pack 6 trace:
(0x01000000):netcomCustomerInstall = (
(0x03000100):customerName = 'VOIP BUND W/DIG TRUNK JPJ357'
)
fix pack 7 trace:
(0x00000000):netcomCustomerInstall = (
(0x03000100):customerName = 'VOIP BUND W/DIG TRUNK JPJ357'
)
xml tag:
<comment comment="fggf" opKey="611490"/>
fix pack 6 trace:
(0x01000000):comment = (
(0x03000100):comment = 'fggf'
(0x03000100):opKey = '611490'
)
fix pack 7 trace:
(0x00000000):comment = (
(0x03000100):comment = 'fggf'
(0x03000100):opKey = '611490'
) |
|
| Back to top |
|
|
| kimbert |
| Posted: Sat Apr 19, 2008 12:43 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| mlafleur, smahon: This is a defect in the product. Please raise a PMR. Please make sure that you mention that this is a known issue ( reference this thread ), so that the IBM service organisation can route your PMR straight to level 3 service. |
|
| Back to top |
|
|
|
|
