No interface in project view
If I import the attached wsdl in soapui a project is generated but without any interface/operation. It should be an interface with 1 operation as intended. This wsdl contains in the schema declaratio...
Forum Discussion
Instead of creating a new project from WSDL, can you try creating an empty project and then adding the WSDL? (just to see if this brings any error messages about)
Then check your soapui.log and error.log. Is there anything relevant?
If I follow your advice I get this exception:
Error loading [http://localhost:81/soap.xsd]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: does not close tag
It relates to the import statement
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/soap/" schemaLocation="http://localhost:81/soap.xsd" />
But I cannot see what should be wrong. And the xsd file actually exists. I can it load in a web browser and I can import the file in my SOA tool and do further work with it, so the source should be syntactically correct.
If you put the contents of your XSD into an XML validator does that tell you anything?
Basically my SOA tool does a schema validation on importing a wsdl but I discovered just now when I import the wsdl the the XML schema of the external schema is also imported implicitly without any error. But when I try to explicitly import the external schema by pointing to exactly that file which is located under http://localhost:81/soap.xsd my SOAP tool generates an error.
null
java.net.MalformedURLException
at java.net.URL.<init>(Unknown Source)
at java.net.URL.<init>(Unknown Source)
at emds.epi.decl.modell.schema.FileSchemaResolver.buildURL(FileSchemaResolver.java:41)My suspicion now points to the soap.xsd schema. But I downloaded it from the w3c (http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.xsd), an official site.
But just discoverd this schema contains another import statement to a further schema (http://schemas.xmlsoap.org/wsdl/).
Basically I just want to refer the "fault" type in my wsdl which is declared in the soap.xsd.
... Not thought that it can be so tricky :-)
An explicit XML valdation tool I don't have. I think I will download and install a test version of xml spy. Hope I will get it working. wait and see what xml spy will have to say.
Now after a few days in learn and know XML Spy and working with that tool in editing the wsdl I got the wsdl working, on my site in SOAPUI and on the site of my business partner but I had to substitute the import statement(s) with the real XSD schema code. I don't know why but I suspect somehow SOAPUI couldn't process the import statements.
But JHunt however a very special thanks to you for your immediatily support. You pointed me to further possibilities in working with SOAPUI.
