Forum Discussion
BA_Service_Haus
13 years agoRegular Contributor
Hi Erik,
right now I opened a ticket to send you the wsdl and schema files.
Please do the following:
- Create a new soapUI project (using these files)
- create a mock service out of the interface
- open a browser and navigate to the wsdl => you will see that the encoding is still defined in the 1st line
- now open any of the imported schema files (node name "import") => now you will see, that the encoding is missing in the first line
When parsing these schema files using an apache library (I guess it migth be Xmlschema-1.4.7.jar), we get a validation error.
We don't get this error, when exporting the mock (Deploy as War) and run it on an WeblogicServer.
There not only the encoding is missing, but also the xml-version (so in fact the whole 1st line is removed).
Best regards
Nico
right now I opened a ticket to send you the wsdl and schema files.
Please do the following:
- Create a new soapUI project (using these files)
- create a mock service out of the interface
- open a browser and navigate to the wsdl => you will see that the encoding is still defined in the 1st line
- now open any of the imported schema files (node name "import") => now you will see, that the encoding is missing in the first line
When parsing these schema files using an apache library (I guess it migth be Xmlschema-1.4.7.jar), we get a validation error.
We don't get this error, when exporting the mock (Deploy as War) and run it on an WeblogicServer.
There not only the encoding is missing, but also the xml-version (so in fact the whole 1st line is removed).
Best regards
Nico