Chandana Napagoda's Blog

Switch statements with String is long waiting enhancement which is requested 1995(Decade before I have joined to IT industry). This String switch statement uses the equal operation to compare the String object in expression and label. Therefore String switch statement is case sensitive. Also according to the Java documentation, this switch statement is more efficient than if-else statements("Java compiler generates generally more efficient bytecode from switch statements"). Ex: public void stringSwitchStatement(String value) { switch (value) { case "Chandana": System.out.println("Input is Chandana"); break; case "OtherValue": case "OtherValue2": System.out.println("Other inputs : " + value); break; case "Test": System.out.println("Input is Test"); break; default: throw new IllegalArgumentException("Invalid input value : " + value); } }

With JAVA SE 7, Multi-catch exceptions handling has been introduced and it is a convinent way for exception handling, since we can catch multiple exceptions using one catch block. In the "Multi-catch" block each exception should be separated by pipe (|) charatcter and that will make code is more readable. Read more :  Working with Java SE 7  Ex: public class SampleClass { public static void main(String[] args) { try { // Your code } catch (ParseException | IOException exception) { // inside the multie catch block } } }

Many SOA governance tools/solutions have not been matured over the years. However, SOA governance tools provided by WSO2 has been improved a lot during the last couple of years. WSO2 Governance Registry provides enterprises with end-to-end SOA governance, which includes configuration governance, development process governance, design and runtime governance, and life cycle management. This enables IT professionals to streamline application development, testing and deployment processes. The latest WSO2 Governance Registry release (5.0), introduces a host of features to further enhance various aspects of SOA governance. WSO2 Governance Registry (5.0) release has a new publisher and store user interfaces to publish and consume assets. Asset owners can publish the assets from the Publisher UI and manage the lifecycle of these assets from this UI, while consumers can discover them from the Store UI. New features of WSO2 Governance Registry: WSO2 Governance Registry is shipped with newly

In WSO2 Governance Registry 5.0.0, we have upgraded Apache Solr version into 5.2 release. With that you can connect WSO2 Governance Registry into an external Solr server or Solr cluster. External Solr integration provides features to gain comprehensive Administration Interfaces, High scalability and Fault Tolerance, Easy Monitoring and many more Solr capabilities. Let me explain how you can connect WSO2 Governance Registry server with an external Apache Solr server. 1). First, you have to download Apache Solr 5.x.x from the below location. http://lucene.apache.org/solr/mirrors-solr-latest-redir.html Please note that we have only verified with Solr 5.2.0 and 5.2.1 versions only. 2). Then unzip Solr Zip file. Once unzipped, it's content will look like the below. The bin folder contains the scripts to start and stop the server. Before starting the Solr server, you have to make sure JAVA_HOME variable is set properly. Apache Solr is shipped with an inbuilt Jetty ser

Today I faced an issue where I am receiving a XML message with duplicate elements. So I wanted to remove those duplicate elements using some condition . For that I came up with a XSLT which does that. My XML input: <OurGuestsCollection  xmlns="http://ws.wso2.org/dataservice">    <OurGuests>       <id>2</id>       <firstname>Sample</firstname>       <lastname>Sample</lastname>       <email>One</email>       <reg_date>2015-02-18T13:59:43.000+05:30</reg_date>    </OurGuests>    <OurGuests>       <id>3</id>       <firstname>Sample1</firstname>       <lastname>Sample1</lastname>       <email>One</email>       <reg_date>2015-02-18T14:13:18.000+05:30</reg_date>    </OurGuests>    <OurGuests>       <id>4</id>       <firstname>Sample1</firstname>       <lastname>Sample1</lastname

One of the use cases of the WSO2 Governance Registry is storing metadata information of different artifacts. In an Organization, there can be different metadata of different artifacts such their REST APIs, SOAP Services etc. In such a scenario you can use API and Service RXT which are available in the WSO2 Governance Registry to store metadata information. With the use of API metadata which is stored in the WSO2 Governance Registry, you can publish APIs into WSO2 API Manager without accessing the web interface of the API Manager. This API creation is handled through lifecycle executor of the WSO2 Governance Registry. Once lifecycle state of the api publisher is reached, the executor will invoke Publisher REST API of the WSO2 API Manager and create the API. "Integrating with WSO2 API Manager" documentation explains about how to create an API using SOAP service meta data information. If you want to create an API using the REST API metadata information available in the WS

In WSO2 API Manager, expiration period of all the access tokens is set to 60 minutes (3600 seconds) by default. However, you can modify the default expiration period value using identity.xml file located in <APIM_HOME>/repository/conf/ directory. In the identity.xml file you can see separate configurations to modify default expirations of User tokens and application access tokens. ApplicationAccessTokenDefaultValidityPeriod If you are planning to modify the validity period of appliccation access token, then you have to modify the default value of the <ApplicationAccessTokenDefaultValidityPeriod> element in identity.xml file. Changing the value of <ApplicationAccessTokenDefaultValidityPeriod> will not affect for existing applications which have alreday generated application tokens. So when you regenerate the application token, it will pick the token validity time from the UI. Therefore, for applications which has already generated tokens, token validity period ne