| Author |
Message
|
| Scorpio_16 |
 Posted: Thu Sep 24, 2009 7:15 am Post subject: XML output in V6.1 |
 |
|
Apprentice
Joined: 15 Dec 2008
Posts: 25
|
We are migrating a flow from v5 to V6.1. Message sets are built using the schema provided.
the problem that I have is the output in V6.1 has an additional namespace (xmlns:xsd="http://www.w3.org/2001/XMLSchema" ) where as v5 doesn't has. other than this rest all data exactly matches.
Does anyone know how to get rid of this additional default NS in V6.1 ?
Appreciate your help.
Thanks |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Sep 24, 2009 7:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Why is it a problem that the namespace declaration is (probably correctly) there? |
|
| Back to top |
|
|
| Scorpio_16 |
| Posted: Thu Sep 24, 2009 7:57 am Post subject: |
|
|
Apprentice
Joined: 15 Dec 2008
Posts: 25
|
| We send the final output xml to thirdparty client which they validate and as a result of this additional namespace their process is failing. They want us to remove this additional namespace. As this is created by broker while sending the xml out, i am quite confused of how to remove this in message flow. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Sep 24, 2009 8:29 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Are you on the latest fix pack? |
|
| Back to top |
|
|
| Scorpio_16 |
| Posted: Fri Sep 25, 2009 5:06 am Post subject: |
|
|
Apprentice
Joined: 15 Dec 2008
Posts: 25
|
BROKER - 6.1.0.3
Toolkit - 6.1.0.3 |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Sep 25, 2009 6:03 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| as a result of this additional namespace their process is failing |
A namespace declaration does not change the meaning of the XML, so it should be completely harmless. What exactly is 'failing'? |
|
| Back to top |
|
|
| Scorpio_16 |
| Posted: Fri Sep 25, 2009 6:50 am Post subject: |
|
|
Apprentice
Joined: 15 Dec 2008
Posts: 25
|
Its not failing in middleware. The client to which we send the output xml is not happy with the additional NS. So is there anyway we can get rid of this in middleware ?
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 25, 2009 7:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Scorpio_16 wrote: |
| So is there anyway we can get rid of this in middleware ? |
You might try defining a default namespace. This would remove the explicit namespace from the elements.
| Scorpio_16 wrote: |
| The client to which we send the output xml is not happy with the additional NS. |
This is exactly the point we're all making. All the elements in the XML are part of a namespace, so until you find out why this apparently harmless feature is causing your client a problem then it's going to be hard to fix it.
What parser are they using to read the XML? Embedded in what language? What issues exactly are they seeing?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Sep 28, 2009 1:32 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Its not failing in middleware. The client to which we send the output xml is not happy with the additional NS |
Yes, I understood that. But we're all very puzzled - the extra xmlns declaration does not change the meaning of the message at all. It does not change the namespace of anything. It is redundant, but it should be harmless.
I just want to be sure that the client has a *real* problem, not an imaginary one.
| Quote: |
| So is there anyway we can get rid of this in middleware ? |
Not if you're using the MRM parser. If you use XMLNSC, you can control the output completely. Plus, XMLNSC is the recommended XML parser in v6.1.
There *might* be an iFix available which removes the extra attribute, but I'm not sure. My recommendation would be to use XMLNSC. |
|
| Back to top |
|
|
|
|
