Test built from WADL fails with "URIException: escaped absolute path not valid"

Hi,

there are fixes related to this in the nightly-build (http://www.eviware.com/nightly-builds), is this the version you are using or the official 3.0.1 release?

regards!

/Ole
eviware.com

I'm using the official 3.0.1 release.  I'll give the nightly build a try and report back.

After downloading the nightly, I see that it gets past that error, but gets a different error.  Even stranger, the regular release also gets the same error, and has gotten past the other error.  Perhaps the reason they get the same error is that I created the project from the nightly, and opened the project from both versions.

The cause of the error I see now is relatively obvious. It's generating an incorrect resource path.  Instead of "/SSAxis/rest/catalog/item/1", it's generating "/SSAxis/rest/catalog//item/1" (two slashes between "catalog" and "item"). Obviously, my apps fails to find that resource.

Note that my service paths are specified as ending with "/" in my CXF annotations (like "/catalog/"), so I imagine I can see why this would be happening. CXF doesn't complain about this, so I imagine this is just something where they fudged my value to "what I obviously meant". I wouldn't be surprised if the spec either says this is invalid or is ambiguous.

After I fixed my path annotations to remove the trailing slash and regenerated the WADL and recreated the project from it, the test worked fine.

Hi,

ok.. thanks for all the info.. I guess soapUI could check that it doesn't join paths like this in the first place.. i'll put it in our JIRA..

regards!

/Ole
eviware.com

Hi,

I have now committed a fix for this, so tomorrows nightly build should solve the issue. Please try it out and let us know how it goes!

Regards,
Dain
eviware.com

Hmm, I downloaded the 20090921 nightly build.  I changed my wadl file back, adding the trailing "/" to "/catalog", then I created a new project from that WADL.  I can tell before I finish creating the project that there's still a problem.  I'm on the "Generate Testsuite" dialog, and in the "Resources" list I see the following two items:

/catalog/: /catalog/
/item/{id}: /catalog//item/{id}

Notice the two consecutive slashes in the second one.  Does that mean it's not going to work, or is this going to be filtered out a later point?  If the latter, it might have been good if this duplication was filtered out by this point.

As I suspected, I continued with the test, and it still failed with the same error.

Curiously, I tried doing a "Help->About" and found the following build id:

  Build soapui-3.0-dist-24-2009-08-09, Build Date 2009/08/09 19:52

Hi,

The filtering is done when the request is to be sent, so it may be displayed with the double slashes prior to that. However, it seems that you aren't using a new build according to the build date. Could it be that you are installing into an existing installation? Please try reinstalling the latest nightly build into a fresh directory and see if that helps.

Regards,
Dain
eviware.com

Actually, you were right that I wasn't executing the version I thought I was, but for a different reason.  I was properly installing them into separate trees, but I somehow managed to create a Windows shortcut with the exact same name as the one for the main 3.0.1 release, and when I edited the shortcut properties for the one that I created to point to the nightly, it simply ignored the changes I made in the dialog, so I was still executing the 3.0.1 release.

However, I'm hitting some obstacles with using the nightly (now the 0922 version).  I first saw an odd limitation with using "..\lib\*" in the classpath setting in the BAT file.  I have no idea why, but I had to change this to an explicit reference to all of the jar files in that directory.  Without that, it simply couldn't find the classes in those jars.

Then, when I finally got my project loaded and started navigating into the project tree, when I double-clicked on "Request 1", the console said this:

java.lang.NullPointerException
       at com.eviware.soapui.support.components.BrowserComponent.setUpProxy(BrowserComponent.java:639)
       at com.eviware.soapui.support.components.BrowserComponent.initBrowser(BrowserComponent.java:251)
       at com.eviware.soapui.support.components.BrowserComponent.getComponent(BrowserComponent.java:161)
       at com.eviware.soapui.ui.URLDesktopPanel.(URLDesktopPanel.java:37)
       at com.eviware.soapui.SoapUI.showPushPage(SoapUI.java:1088)
       at com.eviware.soapui.SoapUI$3.run(SoapUI.java:730)
       at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
       at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
       at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
       at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)

so it didn't bring up the dialog to submit the test request.