Forum Discussion
jijisv
15 years agoNew Contributor
I am also getting the same error.
The error message shown in the screen is
I had a look at the soapUI http log and found that [0xef][0xbb][0xbf] is coming before the xml header declaration in the schema and I am assuming the error message reported by soapUI 4.0 is because of this.
Another interesting thing is that I am able to import the same wsdl in to soapUI 3.0.1. I checked the soapUI 3.0.1 http log also and could see the same above characters before xml header declaration in the schema but soapUI 3.0.1 was not showing any error and it could successfully import the wsdl.
So, I am assuming this an issue with soapUI 4.0. Is there anyway to solve this?
Thanks
Jiji
Tue Jul 19 23:48:55 IST 2011:ERROR:com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:122)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:532)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:562)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:542)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:521)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:226)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149)
at java.lang.Thread.run(Unknown Source)
The error message shown in the screen is
Error loading [http://schemas.mysite.com/xsd/MySchema.xsd] Unexpected element: CDATA on line 1, column 1
I had a look at the soapUI http log and found that [0xef][0xbb][0xbf] is coming before the xml header declaration in the schema and I am assuming the error message reported by soapUI 4.0 is because of this.
Tue Jul 19 23:58:42 IST 2011:DEBUG:<< "[0xef][0xbb][0xbf]<?xml version="1.0" encoding="utf-8"?>[\r][\n]"
Tue Jul 19 23:58:42 IST 2011:DEBUG:<< "<xs:schema elementFormDefault="qualified"[\r][\n]"
Another interesting thing is that I am able to import the same wsdl in to soapUI 3.0.1. I checked the soapUI 3.0.1 http log also and could see the same above characters before xml header declaration in the schema but soapUI 3.0.1 was not showing any error and it could successfully import the wsdl.
So, I am assuming this an issue with soapUI 4.0. Is there anyway to solve this?
Thanks
Jiji