Charitha's Web Log

WSO2 Web Services Application Server (WSAS) provides with a storage manager in which you can persist messages transmitted between RMS (reliable messaging source) and RMD (reliable messaging destination). By configuring persistent RM, you can prevent messages loses even if the server is down. This post guides you through the steps to configure persistent RM in the latest versions of WSO2 WSAS (WSAS-3.*). I assume you have a basic understanding about WS-RM, if not, please read http://www.infoq.com/articles/fremantle-wsrm-introduction first. Pre-requisites Download and install WSO2 WSAS-3.1.1 Persistent implementation of WS-RM will be supported in most of the popular DBMSs. However, I will use MySQL server 5.* in this demonstration. Therefore, install and configure MySQL. Step 1 As the first step, we need to create the persistent storage which is going to be used in reliable message transmission. Lets create a data base and the necessary table as follows. mysql>create database SANDESH...

While developing WSO2 QA test framework (which is based on selenium RC), we wanted to give users the choice of selecting test cases without running whole suite at once. Our plan was to pass a system property during maven test run. However, passing a system property directly through command line does not work since the surefire plugin is run under a different JVM instance that is launched by Maven. In order to overcome this, maven surefire plugin can be configured as follows by specifying the required system property. <systemProperties> <property> <name>test.suite</name> <value>${test.suite}</value> </property> </systemProperties> According to this example configuration, we can run test suite with passing a system property as follows. 'mvn clean install -Dtest.suite=test-case'

The latest version of WSO2 carbon based products were released yesterday. More info can be found at http://wso2.org/projects/carbon New Features in This Release ---------------------------- * Improved transaction support. * Improved Support for deploying on top of WebSphere, WebLogic, and JBoss. * P2 based provisioning for WSO2 Carbon family of products. * Numerous bug fixes.