# XML Document does not Validate

**URL:** <https://techcommunity.softwareag.com/t/xml-document-does-not-validate/58454>\
**Category:** Forum\
**Tags:** Former-Crossvision-Products, Service-Orchestrator\
**Created:** [February 28, 2003, 10:56pm UTC](https://techcommunity.softwareag.com/t/xml-document-does-not-validate/58454 "2003-02-28T22:56:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guest](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/guest/32/75_2.png) [@Guest](https://techcommunity.softwareag.com/u/Guest)\
**Post date:** [February 28, 2003, 10:56pm UTC](https://techcommunity.softwareag.com/t/xml-document-does-not-validate/58454/1 "2003-02-28T22:56:55Z")

</div>

I have another problem and I think this could be something minor or just simply my own fault. In my sequence I validate the incoming XML document and then I evaluate whether the document is valid or not. The problem seems to be that my document does not validate at all. I have used XML Spy and the document is 100% correct (when validated against the schema I’m using). I also went a step further and wrote a script and invoked the xerces parser to validate the document and again it validates 100%.   
  
Why doesn’t the document validate when I run it through my sequence? Please find attached the rather simply sequence:  
  
  
  
 \< !–{Name: ValidateDocument};{Notes: }–\>  
  
  
 \< !–{Name: TestValidateCondition};{Notes: }–\>  
  
  
 \< !–{Name: Transform};{Notes: }–\>  
  
  
 \< !–{Name: ValidDocumentResponse};{Notes: }–\>  
  
  
 \< !–{Name: step};{Notes: }–\>  
  
  
  
  
  
 \< !–{Name: step};{Notes: }–\>  
  
  
 \< !–{Name: step};{Notes: }–\>  
  
  
  
  
  
  
  
  
  
Any ideas what the problem could be?  
  
Regards  
Theo

---

<div class="post-metadata">

**Author:** ![Guest](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/guest/32/75_2.png) [@Guest](https://techcommunity.softwareag.com/u/Guest)\
**Post date:** [March 1, 2003, 3:35am UTC](https://techcommunity.softwareag.com/t/xml-document-does-not-validate/58454/2 "2003-03-01T03:35:42Z")

</div>

I found the cause of the strange behavior I encountered in Mediator. I added a SagLogger step right after the validation step and noticed the following message in the DefaultComponentFactory.xbd.log:  
  
---- Properties -----  
xbd.validator.schemaused = [http://localhost:8080/Sequences/Benchmark/xsd/Patient.xsd](http://localhost:8080/Sequences/Benchmark/xsd/Patient.xsd)  
xbd.validator.isvalid = yes  
xbd.validator.dtdused =   
  
which meant that the XML document did validate correctly and then it hit me. I test with a "TRUE"instead of a “yes” in my if statement in the sequence, it read as follows:  
  
  
  
and should have read:  
  
  
  
After making the change the problem was solved. Silly user mistake after all.  
  
Theo :rolleyes:

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:39pm UTC](https://techcommunity.softwareag.com/t/xml-document-does-not-validate/58454/3 "2021-04-02T14:39:15Z")

</div>


