Lost example request. How to re-create?

Hi,

You need to right-click on the method and click on "New Request". But there does not seem to be a method under your resource.
The request has to be based on the method. So right-click on the resource, then select "New Method" to create the method that you will use there first.

Otherwise, if you had a WADL that had the definition for the missing request, you could create a new project from it.

Regards,

Giscard
SmartBear Support

I did 'New method'. And it created a request. I can't do anything with the request. Not open it no nothing.

I try again new request and added the 2 parameters i need. Once again i cannot open the request Soap UI doesnt work.

Like i do 50 times a day i shut Soap UI down and restart. No i cannot open the request..... It's there not even letting me look at it

I regret buying the program and i am seriously considering filing a claim for this bug-ridden program! I don't have a WADL file. I try to work with Rest request and JSon and it's problem after problem after problem. Most of the time a reboot helps but now crap like this. Ofter added a new Method just freezes. Nothing happens. Try again. Nothing. A reboot and there are 2 Methods!

I am *not* satisfied with this program at all!

Oke after the 50th reset today i finally access my request!

It still does not work. I think the problem is in the level. All my other request have 'Style = Template" and "Level=Method"
This request is 'Style = Template" and "Level = resource"

How do i set Level to Method? I can open the dropdown box but it only holds 1 value.

Oh and here is one to add to your buglist. If i accidently click on the word 'Method' on the level value it immediately changes to 'resource'. I dont select someonething else i just click on it. I cannot change it back anymore. It changed to recource forgood

Now how to i change it back?

Good job changing a value on a click even without possibility to change it back more work for me thanks a lot!

Another one for your buglist

I have 2 parameters for that request. I take 1 and set the Style to 'QUERY"

And it promptly deleted my second parameter! Just make a selection and it removed my other parameter no warning

Hi,

I could not reproduce the issue that you have mentioned, when changing the parameter Style to 'QUERY' (deleting your other parameter). I could not also reproduce the automatic changing of the the Level once you click on 'METHOD'.

Besides that, if you need method parameters, you should create them not on the request but on the method (ex: Get/Post), then the request will inherit the method-level parameters. And then when you look at the request you will see those method parameters with the level indicated as "METHOD".
You may also refer to this article: http://www.soapui.org/REST-Testing/rest-resources-and-methods.html

Regards,

Giscard
SmartBear Support

OK. I did it the way you described. The level is no METHOD but i can only choose Header, Query, Matrix or Plain for Style while i need Template. Not even sure why but if i execute it like this i get "Not JSON content". The old request worked and this seems to be the only thing different.

Why does it need to be so complicated why cant i just select Template. Very poor design

The help here is truly amazing.....

I think i am 1 step further

I get the following error:

Wed Jul 30 15:08:11 CEST 2014:ERROR:java.net.URISyntaxException: Illegal character in path at index 81:
http://xx.xxx.xxx.xxx:8080/api/conversa ... ebda2f00f/{itemId}/evaluate

The problem is i think it does not regonise {itemId}. I checked why not. If i automatically create the request like you told me to it created the field as {itemID} with a capital D at the end. If i execute the comment i see the field for 'b7d167a9-af74-455e-9d59-486ebda2f00f' is converted but the {itemID} is not.

I can NOT change itemID to itemId ANYWHERE. Not in the recource parameters or anywhere else (Another bug you can't 'reproduce' (just call me a liar) i presume)

To make sure I dont set the Method myself. I tried 50 times does not work. If it is auto-create it it makes an uppercase of a lowercase field and so the field is not regonised. The result i need would be something like:

http://xx.xxx.xxx.xxx:8080/api/conversa ... 0/evaluate

Hi,

Are you able to share your project and point out exactly what the issue is? Based off the post it seems to be {itemID} vs {itemId}, but I can't see why or where it would be changing from a capital D to a lowercase d. If you are able to share your project then please open a support ticket and reference your forum post.

http://www.soapui.org/Support/support-overview.html

Regards,
Marcus
SmartBear Support

Well i can't RENAME it but i can remove it and recreate it.

Problem is now i have 2!!!!!! itemId. It is impossible to remove the second itemId. Either BOTH are removed or non at all.

Good job your doing guys! Sold me software i need to reboot for every change i make to take affect but now can reboot as much as i like i am back to where i was a week ago. Well done scamming me out of 400 euro for a non-functioning program!

Not to mention the excellent "Do'h, works on my machine" customer support

I already have a ticket but i noticed i get 'helped' here quicker

I made a movie of the not beeing able to remove a parameter so you can see for yourself! I can remove the whole request and redo it again but each time there is a different issue!!!!!!!!! I am at like bug 8 or 9 now!!!

Can i mail you the video?