Forum Discussion
jasa
15 years agoOccasional Contributor
I was able to find a workaround/solution. This error was caused by using a wrong wadl name space.
I was using:
xmlns:wadl="http://wadl.dev.java.net/2009/02"
=> which did not work and generated the errors
But if I use:
xmlns:wadl="http://research.sun.com/wadl/2006/10"
=> it works
I was using the newer reference to be in sync with the latest WADL specifications.
Is this my mistake or is SoapUI just not compatible with the latest specs?
Thanks.
I was using:
xmlns:wadl="http://wadl.dev.java.net/2009/02"
=> which did not work and generated the errors
But if I use:
xmlns:wadl="http://research.sun.com/wadl/2006/10"
=> it works
I was using the newer reference to be in sync with the latest WADL specifications.
Is this my mistake or is SoapUI just not compatible with the latest specs?
Thanks.
Related Content
- 5 years agowhuang