SoapUI vs junit

Junit is a good option to quickly have unit tests ready, simply by adding custom 'test' target and add <junit> task inside, put whatever classes you want to test, thats it. For java, or pojo's this works best.

However for WebServices soapUI is a simpler option with ui based tests that can be done very quickly. It many features including invalid payloads etc, but you cant configure your real client like situation in soapUI, e.g. Jax-ws based client. It targets to have more interoperable env to test for your service.
In any case, you can always use soapUI to quickly devise and run tests. Later you can create jaxws client from WSDL and write junit for your service.

Jai ho

Google io keynote

Today i watched google IO keynote. I think its history by now, but it was a worth watch. About whats happening in web and google/browser world.
few highlights
1. HTML5 is much powerful with tags like canvas and video for 2D and 3D rendering using browser ONLY.
2. Tried these APIs with eclipse plugin.
Google webtool kit
Google appengine
App engine has got amazing features to manage webapps from your own ISP or from appspot.com. These services are almost free.
3. Google web elements
Jai ho

First blog via mobile

Check this...