I started again to work on Petals Studio 1.3.2, and I am not able anymore to create a Provider SU for a SOAP webservice.
I tried with java 6 SDK and a java7 SDK : same error. i also unzipped again the Petals sudio : same error...
I always get the following : any idea? The symptom is that the jbi.xml is not creted in the jbi folder :(
This error indicates a problem while importing a WSDL dependency (e.g. a XML schema).
Are you sure your WSDL is valid? Is it available somewhere, so that I can test it? Either your WSDL is invalid, or it is not supported correctly (bug).
Since I plan to release a maintenance version of the studio really soon, it is the right moment to fix it.
I have taken your last version and updated the import references.
The WSDL cannot be validated in Eclipse with respect to the WS-I compliance. So, it is valid, but probably not WS-I compliant. And I was able to import it with the studio (no issue or log entry).
I tested a trunk version, a version 1.3.1 and 1.3.2.
I also noticed this WSDL is different from the previous one. The first import is different (not the same namespace). Can you make another test and tell me if you still have errors with this WSDL?
I regenerated the wcf service from scratch.
the WSI compliance has been validated by SOAPUI.
It still fails in Petals Studio
The wsdl ( starting with wsdl:definitions name="n_ws_dba" targetNamespace="http://tempuri.org/") imports another namespace ( <wsdl:import namespace="http://my.company.com" location="http://myserver/ws_dba_wcfservice/n_ws_dba.svc?wsdl=wsdl0" />
) which in turn imports some XSD files.
By configuring IIS, I have flattened all the xsds in the wsdl, but it seems that Petals does not handle the include of a namespace . Is it exact ?
Like I said, the last WSDL you sent me was successfully imported with the studio.
But it is not the same than the first one you sent in this topic. In the first one, there was no import of a namespace "http://tempuri.org/". And the import of the first WSDL failed.
So, right now, I cannot reproduce your problem.
We can make another try if you want. Regenerate the WSDL under the shape you want, reproduce the problem with the studio, and then send me all the WSDL files.
I did the test again on a simple .NET WCF webservice.
In the zip included, all the wsdl and xsd are included (untouched) , + the stack trace in Petals Studio.
I did try to generate the Provider directly from the webservice URI, and also by loading the wsdl file from the filesystem.
I have taken the last WSDL.
The imports are all referenced by URL ( http://accept.xxxx/perfo_wcfservice/n_test.svc?wsdl=wsdl0 ). Since this URL is not available, I have to update the "location" and "schemaLocation" attributes. The resulting WSDL is valid and successfully imported in the studio (version 1.3.2).
I guess that when you loaded the WSDL from the local file system, the WSDL was also referencing the imports by the full URL (and not a relative one). Is that right?
If true, then the only explanation is that there is a bug with the import URL.
I will investigate further this part. ;)