| Author |
Message
|
| sarathsps |
 Posted: Thu May 04, 2006 3:49 am Post subject: Error in Parsing by MRM Parser : Invalid Member for typeCont |
 |
|
Novice
Joined: 04 May 2006
Posts: 19
|
i created XML Message definition files based on the XML Schema files
and i configured the same on the MQInput node with the parser as MRM and given appropoiate Message set.
Eventhough have given the proper structure of the XML message i am getting the Following error : Invalid Member for typeContent closed .. Can this be because namespaces XML Schema files?.
Please help..
Parthasarathy S |
|
| Back to top |
|
 |
| sarathsps |
| Posted: Thu May 04, 2006 3:56 am Post subject: |
|
|
Novice
Joined: 04 May 2006
Posts: 19
|
| I am Using Message Broker 5.0 |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu May 04, 2006 4:50 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi sarathsps,
You got this error during deployment or while running the flow.
You have not given enough information but the error seems to be concerned with some complex type with Content validation set as closed....but the data not conforming to it or something....or perhaps the options u've selected are not allowed...
Regards. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 04, 2006 5:19 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
This is a validation error issued by the MRM parser when it finds an unexpected member of a complex type or group. Are you sure that your input message is valid? ( have you checked with another XML parser? )
If you are still sure that your input message is OK, please post
- the full text of the error, and any other errors which were issued at the same time.
- The fragment of XML which is causing the failure ( or the full message, if it's not too large )
- A description of the complex type identified in the error message (or maybe the fragment of XML Schema which describes it). |
|
| Back to top |
|
|
| sarathsps |
| Posted: Thu May 04, 2006 5:46 am Post subject: |
|
|
Novice
Joined: 04 May 2006
Posts: 19
|
Hi
I Got this error while running the Message flow . The exception is thrown at the MQInput Node.
i have created a Message defination files based on the XML Schema files which has simple and complex types and i am trying to use those Elements in a seperate Message definition file message.
The XML is
<xml>
<DataUp>
<MessageHeader>
<MsgID>0990 </MsgID>
</MessageHeader>
</DataUp>
</xml>
The XSD's are
<?xml version="1.0" encoding="UTF-8"?>
<import namespace="http://esb.tAt.com/schema/ReferenceV1" schemaLocation="../ReferenceV1.xsd" />
<complexType name="MessageHeader" >
<sequence>
<element name="MsgIDID" type="ref:MessageID" />
</sequence>
</complexType>
</schema>
----------------------------------
<schema
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:mes="http://esb.tgt.com/schema/MessageStructureV1">
<element name="DataUpSync">
<complexType>
<sequence>
<element name="MessageHeader" type="mes:MessageHeader">
</element>
</sequence>
</complexType>
</element>
</schema>
---------------------
The Exception thrown is : Invalid Member for typeContent closed : Dataup : MessageHeader
In the message set all are columns are having Minoccurs and Maxoccurs value as 1.
Thanks in advance
Parthasarathy S |
|
| Back to top |
|
|
| madi |
| Posted: Thu May 04, 2006 6:14 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
| Quote: |
The Exception thrown is : Invalid Member for typeContent closed : Dataup : MessageHeader
In the message set all are columns are having Minoccurs and Maxoccurs value as 1. |
that obviously means something is wrong with the input xml
have you tried to see if the xml is valid using a tool like xml spy or something??
im sure u will find the message to be invalid 
--madi |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 04, 2006 6:17 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| <element name="MsgIDID" type="ref:MessageID" /> |
Not sure whether "name=MsgIDID" is a typo. If not, it would explain the error ( because in the XML the element is called MsgID ). |
|
| Back to top |
|
|
|
|
