DOM Parsing Exception in translator. Dequeuing is failing

Question

Hi,
-> I am working on EDI HIPPA File Protocol.
-> My b2b configuration is working. I am getting the payload xml in IP_IN_QUEUE.
But ESB with AQAdaptor is failing giving the below Exception.
-> ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:202) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: Expected name instead of >. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1151) at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1928) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1276) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:197)
-> I have taken the payload xml from rejectedMessages folder from SOA HOME and written a DOM Parser program
to parse that file.It is throwing org.xml.sax.SAXParseException.
-> I validated this xml with xsd I provide both in Oracle B2b config and in ESB using Altova software, it is throwing errors saying the xml is not valid.
-> So I understood that xml which is gettign generated is not the valid one.
Could you please tell me if I have to make any changes.
Thanks
Praveena

Answer 1

Hi Dheeraj,
I did this, I have selected Oracle Integration B2B while generating the xsd, then saved the xsd and then saved ecs.
I gave these ecs and xsd file in my Oracle B2B configruation for Document protocol page.
Then also, I parsed the file which is generated.It is failing in parsing.
I can see that set of empty tags <></> are getting generated before <Segment-SE> tag and after <Loop-2000> as shown below:
</Loop-2100></Loop-2000>&lt&gt&lt/&gt<Segment-SE><Element-96>
(I don't why I am able to see symbols for tags when I am editing this message but once I save the message it is not shown in the forum.actually empty tags are getting geneated.)
I removed these empty tags and parsed it again, then it is parsed successfully.
Could you please tell me what I need to do for not generating these extra empty tags.
my xsd looks as below(pastign for this particular part:
<xsd:element name="Transaction-835">
<xsd:annotation>
<xsd:documentation>Health Care Claim Payment/Advice</xsd:documentation>
<xsd:documentation>This Draft Standard for Trial Use contains the format and establishes the data contents of the Health Care Claim Payment/Advice Transaction Set (835) for use within the context of the Electronic Data Interchange (EDI) environment. This transaction set can be used to make a payment, send an Explanation of Benefits (EOB) remittance advice, or make a payment and send an EOB remittance advice only from a health insurer to a health care provider either directly or via a financial institution.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Internal-Properties" minOccurs="0"/>
<xsd:element ref="Segment-ST"/>
<xsd:element ref="Segment-BPR"/>
<xsd:element ref="Segment-TRN"/>
<xsd:element ref="Segment-REF" minOccurs="0"/>
<xsd:element ref="Segment-DTM" minOccurs="0"/>
<xsd:choice maxOccurs="2" minOccurs="2">
<xsd:element ref="Loop-1000A"/>
<xsd:element ref="Loop-1000B"/>
</xsd:choice>
<xsd:element ref="Loop-2000" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Segment-SE"/>
</xsd:sequence>
<xsd:attribute name="Type" default="Transaction" type="xsd:string"/>
<xsd:attribute name="XDataVersion" fixed="1.0" type="xsd:string"/>
<xsd:attribute name="Standard" fixed="HIPAA" type="xsd:string"/>
<xsd:attribute name="Version" default="V4010X091A1" type="xsd:string"/>
<xsd:attribute name="GUID" default="" type="xsd:string"/>
<xsd:attribute name="CreatedBy" type="xsd:string"/>
<xsd:attribute name="CreatedDate" type="xsd:dateTime"/>
</xsd:complexType>
</xsd:element>
Edited by: Praveena Paruchuru on Mar 10, 2009 6:33 AM
Edited by: Praveena Paruchuru on Mar 10, 2009 6:49 AM