Forum Discussion
Hi Rao,
The WSDL in question does not have inline schemas or referencing any external schemas.
The code is quite simple:
WsdlProject project = new WsdlProject();
WsdlInterface [] wsdls = WsdlImporter.importWsdl(project, wsdlUrl); /* It throws an exception here */
-Peter
- plieu10 years agoOccasional Contributor
Hi Rao,
Just a small correction to my code, this is how it looks:
System.setProperty("soapui.loader.username", userid);
System.setProperty("soapui.loader.password", password);
WsdlProject project = new WsdlProject();
WsdlInterface [] wsdls = WsdlImporter.importWsdl(project, wsdlUrl); /* It throws an exception here */
Thank you.
-Peter
- nmrao10 years agoChampion Level 3
Your reply "The WSDL in question does not have inline schemas or referencing any external schemas." is confusing because Wsdl either have inline or external schema.
One more thing is that not every one gets the mentioned exception. So only possibility here is to get the wsdl be reviewed from your team as it says InvalidDefinition.
Did you happen to see the wsdl correctly in the browser(after providing the credentials) or in soapui first? Just locate the issue at the right place.If that is successful, then it can be further looked into your code.
- plieu10 years agoOccasional ContributorHi Rao,
Sorry about the confusion, I meant that the WSDL does not reference any external schemas.
I saw the WSDL correctly in the browser after providing the credentials. I then tried the SoapUI GUI and saw the WSDL correctly as well with providing the same credentials.
The problem only exists when accessing the WSDL from the code. When I saved the WSDL locally and ran the same code against the local WSDL it works fine.
Related Content
Recent Discussions
- 8 days agoemoya