XML/XSD :: NV-009 :: Ambiguous content model in schema

, ,
1

Hello,

I am using pub.schema.validate to check xml data with a schema imported in Developer using an appropriate xsd file. While trying to validate data corresponding the following schema in my xsd file:

<xsd:element name="LOG">
        <xsd:complexType>
            <xsd:sequence maxOccurs="unbounded">
                <xsd:element ref="ers:DEP" minOccurs="0"/>
                <xsd:element ref="ers:FAR" minOccurs="0" maxOccurs="unbounded"/>
                <xsd:element ref="ers:RLC" minOccurs="0" maxOccurs="unbounded"/>
                <xsd:element ref="ers:LAN" minOccurs="0"/>
            </xsd:sequence>
            <xsd:attribute name="IR" use="required">
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:length value="12"/>
                        <xsd:pattern value="[a-zA-Z]{3}[a-zA-Z0-9]{9}"/>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:complexType>
</xsd:element>

the pub.schema.validate throws the following error:

errorCode: NV-009
errorMessage: [ISC.0082.9015] Ambiguous content model in schema - not LL(1)

Using XMLSpy, it says it is well formed and validates the XML.
I am using webMethods 7.1.2 with IS_7.1.2_WebSvcsXML_Fix15. I took a look to Fix16 but it does not resolve my problem.
Many posts here are about the same problem with no issues.

I remark that I can not change my xsd file and validating the xml using a document instead of the schema does not work very well, it allows many attributes that are not in my schema.

It is very urgent, so any idea is welcomed.

Thank you

2

If I recall correctly, the problem relies on maxOccurs=“unbounded”, it is a limitation on wM implementation.

Modify XSD and regenerate docType, set for example maxOccurs=“1000” and if my memory does not fail, it should work.

If you cannot modify the XSD and regenerate it, you are in big trouble :smiley:

3

Actually I did that just to see if it works or not. It does not resolve the problem.

What I am going to do is to write a java service which will use the xsd and sax parser to validate xml files. It should works. So I do not have to use pub.schemaValidate to validate files.

What do you think?