sumedha's blog

Step 1: Database configuration for registry

   <dbConfig name="wso2registry">
        <url>jdbc:postgresql://localhost/[DATABASE-NAME]</url>

Scenario

Your organisation has an internal Order Management System (OMS). Whenever a customer wants to place an order,it's the internal staff who can access the system and create it. During a planning meeting, this closed nature of OMS has been identified as a barricade for future expansions. It was decided to let an outside development community to access OMS's data & encourage them to write applications based on it. Along with this change, planning team has also identified that monitoring Order data is equally important as well.

By default,Maven source plugin only packs & uploads java sources & resources defined for a given project. When doing so, it gives very little control to the user to select/deselect the source artifacts that should be included/excluded in the pack. May be this was intentional. But when it comes to creating source distributions for WSO2 carbon based products, we needed more control. Hence we modified the Maven source plugin so that we have more configuration options & did an internal release bearing version number 2.0.4-wso2. This modified plugin is available[1] in WSO2 maven repository.

In a componentized project, functionality comes from different components. A full source distribution for such project needs to contain sources from each of these components. Hence it's somewhat challenging when it comes to creating a source distribution. Read on to find out one possible solution.

Let me give you a generic overview of the project structure first.

Using pluggable componentized model to add up features to a project has many advantages. But it sure does introduce many challenges at every aspect of development,marketing,pricing,etc... I have been closly associated with new componentized model(OSGi based) we recently announced @ WSO2. While there can be many, here are some of the evident challenges we faced when creating the distributions.

Introduction

This is the first one in a series of tutorials on explaining how to extend WSO2 Carbon UI framework & add functionality to WSO2's family of products based on WSO2 Carbon framework.

Applies to : WSAS 2.3(and bellow), DS-1.0.1(and bellow)

Background

I will be using the NestQuerySample.dbs created in 'How to use Data Service nested query feature?' for this example.