Author |
Message
|
integration |
Posted: Thu Jul 12, 2007 1:35 am Post subject: Messageset problem while parsing |
|
|
Apprentice
Joined: 26 Jun 2007 Posts: 32
|
Im facing the problem with message set while parsing the output file at the resetcontent descriptor node....
this the error encountered in the exception tree...
Please let me know the solution for this as early as possible..
Number = 5407
Text = XML Parser: Element with a Namespace found when Namespaces are not enabled for the Message Set. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jul 12, 2007 1:38 am Post subject: Re: Messageset problem while parsing |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
integration wrote: |
Number = 5407
Text = XML Parser: Element with a Namespace found when Namespaces are not enabled for the Message Set. |
I'd say the problem is that you've not enabled namespaces in the message set, resulting in the above error when a namespace is encountered.
I'd enable namespaces in the message set or remove namespaces from the XML being parsed.
There's not much else to say given the rather sparse information in your post. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
integration |
Posted: Thu Jul 12, 2007 1:50 am Post subject: |
|
|
Apprentice
Joined: 26 Jun 2007 Posts: 32
|
Hi Vitor,
I have enabled the namespace usage while creating the messageset using xsd, at the reset content descriptor node iam parsing the message with xmlns |
|
Back to top |
|
 |
wbi_telecom |
Posted: Thu Jul 12, 2007 9:55 am Post subject: |
|
|
 Disciple
Joined: 15 Feb 2006 Posts: 188 Location: Harrisburg, PA
|
Can you share the values you have in RCD node? I would create a message set and then use the MRM domain. If you want to use XMLNS you need not create a message set.
Cheers, |
|
Back to top |
|
 |
kimbert |
Posted: Thu Jul 12, 2007 11:19 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
This exception is nothing to do with parsing. It is only ever issued by the MRM parser when it is writing ( outputting ) an XML message.
So, it almost certainly true that:
a) Your message tree contains elements which have namespaces
b) The message set identified in OutputRoot.Properties.MessageSet does not have namespaces enabled.
I would check that you have specified the correct message set. |
|
Back to top |
|
 |
|