Recreate request does not keep values

Hi!

works ok for me.. are you running the latest 2.5.1 build? Can you add the request with the email just before you would recreate the request so I can try from there?

regards!

/Ole
eviware.com

now i am using 2.5.1, same problem.

I have sent the project to a college and can reproduce at his SOAPUI install.
I can reproduce error again and again.
I have attached a screen recording of me reproducing the error.

/Michael

I have the same problem exactly. I've had this issue since version 2.0.2 and just forgot about and sort of accepted that it was like that. It's still present in the 16-feb build of 2.5.1

any news on this ??
this does that i can not update wsdl definition without losing all the values set on requests, even if i update to the same wsld version all values are gone because the keep values is not working.

That in fact leaves the product useless for me as i have to recreate all the testcases when wsdl changes.

if you want project and wsdl files send contact me at
mwl at it-practice dot dk

Hi!

Has the namespace changed in the updated wsdl? If so, this is expected behaviour, the updating of requests in this scenario requires the same namespace/element/node structure to work. soapUI Pro has refactoring functionality (http://www.soapui.org/userguide/interfa ... oring.html) for handling this, check it out.

If the namespace and element/node structure is the same in both the old and new wsdl, then this sounds like a bug, so I kindly ask you to attach the old and new wsdls, together with a sample message that is not getting updated correctly, so I can reproduce and fix!

regards!

/Ole
eviware.com

The wsdl have not changed at all, i update with excactly the same wsdl.
recreate vlaues does not work.
but it seems it works on the mandatory fields though.
i have attached screen recording of problem and project files for you.

it seems the video file is too big :-( (3.3mb)
contact me if you want it
mwl at it-practice dot dk

Same issue as Michael. On some messages the recreate with values work fine and on some they don't. I think it's a complexity issue. Simple ones, like the shakespeare service, work fin and complex ones fail.

I've attached a project with a before and after method, wsdl files and logs. The logs show no errors at all.

Hi!

ok.. thanks.. I'll dig in.. in the meantime, have you tried the refactoring functionality here, it should work better!?

regards,

/Ole
eviware.com

eviware support wrote:
in the meantime, have you tried the refactoring functionality here, it should work better!?

Yes, It seems to work fine. We have refactored several services without issues since you made that fix last week

Hi Jacob,

ok.. sorry for taking so long here.. the problem is that the element you are updating is optional, and since you are not selecting to recreate optional elements when recreating the request those will not be preserved either. You have 2 options:

1) Choose to recreate optional elements, which will preserve the value but also put a '?' in all others
2) Use refactoring functionality in soapUI Pro

Hope this is understandable :-)

regards!

/Ole
eviware.com