I am new to this tool, Can any one help me how to test webservice using this tool,

On #3, I actually think that generating JUnit stubs from soapUI would somewhat defeat the purpose of developing JUnit classes, which is to allow service providers to perform all the steps that service consumers would have to go through in order to consume a service. And I’m pretty sure that you already have enough on your plate with all the other work on soapUI :)

Thanks for the great tool,
Alexander

nice post! I would like to add some more twists:

1) Using a tool like soapUI is mainly for testing the actual server-side web service implementation, and does give some possibilities that are not available (or at least not easy) in JAX-WS;
- sending of invalid messages (both syntactically and structurally) which is usefull for testing server-side error handling,
- sending of messages using standards not supported by JAX-WS (much of the WS-XXX soup)

2) Often when developing web services, you have little control of the actual client technology used on “the other side”, thus providing examples based on JUnit/JAX-WS could be rather limited as there are so many more technologies in use for accessing web services (but of course its better than no examples at all).
-> We have actually had several soapUI users that provide comprehensive soapUI projects together with their web services, since it is a great way of giving a “platform-neutral” example of how the web service is supposed to work. Sometimes they also include a complete Mock Implementation of the web service in soapUI, which allows their client to build/test client code without having access to the actual live service

3) Anyhow, using JUnit as you describe is a great complement and as you say gives an insight in how the web service may be “perceived” by the client. Maybe we could add support for generating stubs for these kinds of JUnit testcases for JAX-WS from within soapUI?

rock on!

kind regards,

/Ole
eviware.com