Forum Discussion
Thanks for your response. As you suspected this option won't work for me, I need to add this WADL to couple of existing Ready API Projects which already use large number of Ready API specific features.
Any way for the time being I'm just adding REST services from URI instead of WADL import. Going forward, it would be nice to get a fix if it's indeed an issue with Ready API.
If there is indeed something wrong with the WADL( atleast from the perspective of Ready API ), it would be nice to know that too.
Regards,
Gilu Gopi
https://support.smartbear.com/product-list/
- DavidV8 years agoNew Contributor
gilugopi, I'm having the same issue in 1.8.5.
Did you end up opening a ticket to the support team? Maybe you could add it here for reference...
- gilugopi8 years agoContributor
- MarcusJ8 years agoModerator
Hi,
I imported the attached customer.xml into SoapUI 5.2.1 open source and I did not get any errors, but no endpoints were created either. Which version of SoapUI was customer.xml able to import into successfully?
DavidV If you haven't opened a support case yet and can post your WADL file then upload it here.
Regards,
Marcus
SmartBear support
Related Content
- 9 years agoelorden1
Recent Discussions
- 22 hours agodipsthorat
- 2 days agoisbiat
- 3 days agoarmygrad