Not able to Validate Multiple XSD's (XSD embedded with another XSD) in Parse XML

Hi All,

Hope you are doing well!!!

We have a requirement where in we have to validate the data in a single XML with Multiple XSD's (Meaning a main XSD has another XSD embedded which is called by using Import).

I expected this to work when i placed both the XSD's on a common server path and refer the same in the schema URL field(in XML Tab) in Parse XML but am getting following error message everytime when i tried that,

** FAIL : Unable to apply Rule-Parse-XML instance. Failed to parse XML. Error: Premature end of file.

I tried by first creating a Parse XML using these XSD's using Meta data wizard and then use the same for validation but am, unfortunately, getting the same error.

Am trying to figure out the other possibilities before going ahead and raise an SR.

I would appreciate if you can help me in figure out the issue!!!




Keep up to date on this post and subscribe to comments

April 15, 2019 - 1:54pm

I've seen use cases for this many times, so I know its feasible. I've always used the following approach.

Place all files in a directory off prsysmgmt .. such as testXML. This folder needs to contain the root xml file (or WSDL which is what I'm usually working with). The embedded files need to be in relative paths off this directory (depending on how they're referenced in import statements).

Then, you test this by loading the root file in IE ... hostname:port/prsysmgmt/testXML/parent.wsdl. If that loads without error, then you can reference same URL in integration wizard of Pega.

My experience is its best to have a Web Server serve up the files as in this above scenario as opposed to having the wizard open files directly.


April 16, 2019 - 8:57am
Response to PaulGentile_GCS

Also, check the PegaRULES file to see where the EOF is happening. If it looks something like this example below, then you're most likely having "’network connection refused’" issue. This indicates the file is null or empty.

Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.
at Source)
at Source)
at Source)

April 16, 2019 - 4:44pm

Hi Paul,

Am getting exactly the same error on Pega logs what you mentioned in your comment. 

Am quite sure that the XSD file is present on the server path and its not empty.

I gave an absolute server path on Schema URL for Validation. Not able to figure out why it is throwing that error.



April 17, 2019 - 11:41pm
Response to SyedMohammedshahQ

What application server are you on? If you place a zip file in the same location, will the Pega Import wizard be able to read it? You could use a benign Product file with test rules.

May 31, 2019 - 10:49am