Forum Discussion

SteveSinger's avatar
SteveSinger
New Contributor
13 years ago

Resource Not Found Error -- REST Services with WADL

Using SoapUI 4.5.1

We are having a problem testing RESTful services. I create a new SoapUI project and point to the WADL (from a Jersey implementation). SoapUI finds the RESTful services fine, parses everything correctly. It creates all the resources, all the methods (including the correct parameters), and creates a request.

However, when I go to actually run the request, it always generates a "The requested resource (Not Found) is not available" error.

I'm not sure what I'm doing wrong -- how can SoapUI find the service to generate all the project artifacts, but then not be able to find it when it goes to run the request?

Thanks in advance

1 Reply

  • FYI, I have resolved this and am posting the info in case anyone else has this same issue!

    The problem is that when the Resource Path is resolved from the application.wadl from Jersey, it appends an extraneous "/" to the front ot the resource path. This causes the problem. Simply go into each resource and remove the first "/" from the name and everything will work fine.