Showing posts from March, 2008

Invoking a public web service programmatically using WSO2 WSAS

A Web service is defined as "a software system designed to support interoperable interaction over a network." Web services are referred to as Web APIs that can be accessed over a network and executed on a remote system hosting the requested services. There are many publicly available web services which can be invoked remotely using client applications. is such a site that hosts different types of public web services. I'm going to demonstrate how such web service is invoked programmaticaly using WSO2 Web services application server (WSO2 WSAS) WSo2 Web services application server provides set of tools to interact with web services. You can download the latest version from here . I'll use a public instance of WSO2 WSAS to generate client side code (stub). You will also try out WSAS public instance before downloading the server. Step 1 First, we may access webservicex to identify a suitable web service which can be invoked remotely. You may see &

Reasons to repeat tests

We usually need repeating certain type of tests in project testing cycles. James Bach explains the reasons to perform repetitive tests in this great article . A must read for anyone interested in SQA/testing!

Secure web services: Signing SOAP messages using WSO2 WSAS and Apache Rampart

In my previous blog post, I demonstrated how Axis2 or WSO2 WSAS web service is deployed and invoked securely with user name token authentication. Here I'm going to invoke the same web service by signing the SOAP messages using server/client keystores instead of username tokens. When signing soap messages in this way, we can ensure; Non-repudiation No tampering of the messages However, this can not be considered as a good mechanism for confidential message transmission since the message contents are not encrypted. Scenario We need to invoke the default version service in secure manner. For that, we are supposed to use two different keystores for client and service. Client uses the client keystore to sign the SOAP request and server responds by signing the reply message using server keystore. Step 1 First, we need to create two separate keystores for client and server. Java keytool can be used to generate keystores. Create client keystore Open a command window (or shell in linux) an