Layer7 API Management

Expand all | Collapse all

Xml schema Validation

Jump to Best Answer
  • 1.  Xml schema Validation

    Posted 04-20-2017 06:19 AM

    Hi Team,


    1.Does API gateway ignores subsequent import statement which are having same namespace during schema validation at runtime? 

    2.Does API Gateway xml processor requires all schema files into one file which are having same namespace for schema validation or it allows multiple namespace?

    Do we have to compress out schema into one-file per namespace?


    For example: We have total 17 schema files sharing which are sharing same namespace.

    So when it parses second schema file ,Is gateway able to validate or ignore the file as it is having same namespace. Will gateway ignore rest all 16 schema files?

    As we are able to import all the schemas into Manage Global resource, but when we are doing schema validation ,it is giving error as below.


    <l7:policyResult status="Bad Request" xmlns:l7=""; xmlns:l7p="">;

                   <l7:assertionResult assertion="l7p:SchemaValidation" status="Bad Request">

                      <l7:detailMessage id="5612">Validating Request</l7:detailMessage>

                      <l7:detailMessage id="5604">Schema validation failure: src-resolve: Cannot resolve the name 'xyz: abc.ValueTypeAbstraction' ' to a(n) 'type definition' component.</l7:detailMessage>


                   <l7:assertionResult assertion="l7p:All" status="Bad Request"/>



    Do we have to compress out schema into one-file per namespace?

  • 2.  Re: Xml schema Validation
    Best Answer

    Posted 04-21-2017 11:49 AM



    Good day. When using schema validation, the import statement is meant for bringing in schemas with a different namespace whereas include is for schemas with the same namespace.  Without seeing the schemas, if they are using the import statement it may have problems aligning the right schema to use.




    Stephen Hughes

    Director, CA Support