WSO2 Data Services v2.2.0 released

WSO2 Data Services Server team has recently announce the release of version 2.2.0 of the WSO2 Data Services Server.

The WSO2 Data Services Server is an extremely simple and elegant mechanism to take data and make it available as a set of WS-* style Web services or as a set of REST style Web resources. It augments SOA development efforts by providing an easy to use platform for creating and hosting data services. This enables easy integration of data into business processes, mashups, gadgets, BI applications and any service in general.

Why should you use the new version?

Support for large XML outputs - http://wso2.org/library/knowledge-base/large-scale-data-transfer-data-services-streaming
Google Spreadsheets as a data source - http://wso2.org/project/solutions/data-services/java/2.2.0/docs/google_spread_sheet.html
Content filtering based on user roles - http://wso2.org/library/articles/content-filtering-data-services-user-roles
Support for named parameters
Ability to configure schema type for output elements
Mixing multiple data source types in nested queries
Excel 2007 support
Support for Oracle Ref Cursor - http://wso2.org/library/tutorials/use-oracle-ref-cursors-wso2-data-services-server

Comments

Overriding default look and feel of GREG - 5.3.0

Following list explains what are the best approach for different use cases. 1 ) - You created a new asset type, and you need to change the look and feel of the details page in the listing page just for that new asset type. To create a new asset type you need to login to the carbon console (username:admin, password:admin) https:// :9443/carbon/ Navigate to Extensions > Configure > Artifacts Click "Add new Artifact" link at the bottom of the page. By default in the "Generic Artifact" area "application" asset type is loaded. Note the shortName="applications" in the root node. "applications" is the name of the asset type. Browse in to /repository/deployment/server/jaggeryapps/store/extensions/assets Create a folder with name "applications" Now we can override the files in /repository/deployment/server/jaggeryapps/store/extensions/app/greg-store-defaults Since we are overriding the details page we need to...

Simple client side validation library

Client side validation has never been easy.. Include jQuery and the validator.js < script src = " http://code.jquery.com/jquery-1.11.3.min.js " ></ script > < script src = " ../validate.js " ></ script > Simple validation < form id = " myForm " > < label >User Name < span class = " red-star " >*</ span > </ label > < input type = " text " name = " userName " class = " validate-required " /> < br /> < label >Password < span class = " red-star " >*</ span ></ label > < input type = " password " name = " password " class = " validate-required " /> < br /> < input type = " submit " value = " Login " /> </ form > ...

Role of GREG permission-mappings.xml

GREG has a permission-mapping.xml. We can find it at /home/chanaka/Desktop/greg/wso2greg-5.2.0/repository/conf/etc/permission-mappings.xml Each entry has three attributes. managementPermission resourcePermission resourcePaths Ex: managementPermission="/permission/admin/manage/resources/govern/server/list" resourcePermission="http://www.wso2.org/projects/registry/actions/get" resourcePaths="/_system/governance/trunk/servers" /> There are default configurations in this file. These entries are mapping each permission in the permission tree in to resource paths and assign them permissions. With the above line in the permission-mappings.xml, an admin user who assign the permission " /permission/admin/manage/resources/govern/server/list " will be able to do get operations on registry resources stored at " /_system/governance/trunk/servers ". We can provide multiple resource paths by separating them by comas. There...

My Notes

Search This Blog