Analytic module in latest SmartClient releases provides charting feature, but its not available under LGPL license. In this post we will discuss about how to integrate third party javascript charting API with smartclient.

Following are the key objectives:

Component Based Approach: Charting feature must be designed using component based approach, so that charting component can be reused at several places. We will call this component as 'SmartChart' in rest of this post.

Data integration: Smartclient's DataSource provides data integration capability which can be plugged in at ease. Smartchart uses datasource for integrating with server.

Third Party Charting JS API: We are using DOJO charting API for now, but later we will try to integrate other opensource charting APIs.

We have been using JManage in our development environment since few months and wefound it to be an excellent web based JMX client for managing and monitoring Java applications. It is opensourced, the code is very well written, easy to understand and change.

Few notable features that it provides

It can send Email Alerts when your application goes down or you need to watch a MBean attribute.

Dojo fails in its online documentation. JQuery seems to do a much better job with documentation and examples. Dojo is must more robust than JQuery. Development using JQuery is much faster than as compared to Dojo. JQuery is an extenstion of Javascript and programming model is the same. While Dojo is a kinda toolkit and learning programming model needs an extra effort.

This post is about, how to generate Cobertura Coverage Reports with some insides of Cobertura. In the later section we will discuss steps to report generation for a  web application deployed on Tomcat container.

Code Coverage

Code coverage is a measure used in software testing. It describes the degree to which the source code of a program has been tested. It is a form of testing that inspects the code directly and is therefore a form of white box testing.

Overview

In our application we used RBAC approach for implementing the authorization in our security data layer. User roles and permissions were modeled as separate entities. We had a requirement of providing sub-roles to a given role, with which a user assigned super role will be permitted for permissions associated to that particular role and all sub roles as well.

To store this hierarchical data we modeled a rolesubrole entity which stores subroles associated to a given role.
Loading