i have to validate xml message.But i do not have XSD. So in message model i created xsd with the xml .With this xsd i created message set and try to validate xml.how can i resolve this problem . my flow start with http input node . failure and catch terminals of the http input node connected to error handler subflow.but i am not receving the message to subflow.while validating with incorrect xml i am getting following exception.i am using message broker v8.0
?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<faultstring>BIP3113E: Exception detected in message flow testflow (broker MB8BROKER) </faultstring>
BIP5009E: XML Parsing Errors have occurred
BIP5025E: XML schema validation error ''cvc-complex-type.2.4.a: Expecting element with local name "plancode" but saw "pla".'' on line '1' column '55' when parsing element ''/Root/XMLNSC/publishproducts/products/product/productinfo''. : F:\build\slot1\S800_P\src\MTI\MTIforBroker\GenXmlParser4\ImbXMLNSCDocHandler.cpp: 702: ImbXMLNSCDocHandler::handleParseErrors: ComIbmWSInputNode: publishproduct#FCMComposite_1_1</text></detail>
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2012-10-30T09:43:37Z by firstname.lastname@example.org
Pinned topic XMl VALIDATION
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-30T09:43:37Z at 2012-10-30T09:43:37Z by email@example.com
firstname.lastname@example.org 120000CJSH515 PostsACCEPTED ANSWER
Re: XMl VALIDATION2012-10-30T09:43:37Z in response to Rahul05This is a question about error handling in HTTP flows, right? You want to know why your error handling subflow is not being called when there is an error in the flow.
Have you taken a debug-level user trace to find out what the flow is doing - it may give a clue about why it is doing this.