I have to mock quite complicated java web service and I’m searching for the right solution. One way to do it would be to use Soap UI, but I need something that would be able to modify server state ie. one request would affect future requests.
In this particular case it could be done quickly by saving serialized objects to disk and sometimes spawning asynchronous responses to the originating client webservice.
Those two requirements are preventing me from using SoapUI – the groovy logic would become quite complicated and probably hard to mantain.
My questions:
1) Are there any other SoapUI advantages in this context (eg. easy migration to new version of wsdl) over custom java mock implementation?
2) What would be most appropriate way to generate the webservice from wsdl and still be able too hook up with some custom functionality, ie. by attaching some hooks that would be editable in seperate files (to facilitate further ws code regeneration from updated wsdl)?
For simple mocks I use soapUI, while for more complicated when state must change between request I use simple web service emulator written in Python. Such emulator use reply templates created from real web service or responses I created in soapUI. This way I can control all logic.
Emulator for my last project has 300+ lines of Python code, but for previous, much simplier, it was ~150 lines of Python code.