Skip to main content

Choosing Java reporting tool

My current goal is to obtain an universal solution to be able to export application data in any format I'd prefer. Mainly it includes exporting tables with various data.

I've done an overview and have considered the following alternatives:
  1. Own implementation.
    Here I mean implementation of own Java library that will accept some abstract data (say, valuelist) and will perform export using known open-source libraries (MS Office Excel - Apache POI, PDF - itext, etc). This is the way we've already used at work before.

    The critical disadvantage of this proposal is that much efforts will be required.
  2. Existing solution.
    This is also known as reporting engine software.

    Main points:
    • JasperReports is the most popular open-source reporting engine.
    • There are 3 ways to use it:
      • JasperReports API - gives complete control on report creation but is extremely complex.
      • Different visual report designers (e.g. iReport) - allows creating report templates manually.
      • Software tools that use JasperReports API and allow generating reports during run time (no visual designer is required).

Definitely the last point is what I need at the moment. There are two alternative quality solutions here:
  1. DynamicJasper
  2. DynamicReports
They are quite similar and each has its own pros and cons. Although the first is recommended in this comparison, I suggest implementing a simple prototype report for both alternatives to come up with the final choice. Probably it'll be described in the next post.

Comments

Popular posts from this blog

DynamicReports and Spring MVC integration

This is a tutorial on how to exploit DynamicReports reporting library in an existing  Spring MVC based web application. It's a continuation to the previous post where DynamicReports has been chosen as the most appropriate solution to implement an export feature in a web application (for my specific use case). The complete code won't be provided here but only the essential code snippets together with usage remarks. Also I've widely used this tutorial that describes a similar problem for an alternative reporting library. So let's turn to the implementation description and start with a short plan of this how-to: Adding project dependencies. Implementing the Controller part of the MVC pattern. Modifying the View part of the MVC pattern. Modifying web.xml. Adding project dependencies I used to apply Maven Project Builder throughout my Java applications, thus the dependencies will be provided in the Maven format. Maven project pom.xml file: net.sourcefo

Connection to Amazon Neptune endpoint from EKS during development

This small article will describe how to connect to Amazon Neptune database endpoint from your PC during development. Amazon Neptune is a fully managed graph database service from Amazon. Due to security reasons direct connections to Neptune are not allowed, so it's impossible to attach a public IP address or load balancer to that service. Instead access is restricted to the same VPC where Neptune is set up, so applications should be deployed in the same VPC to be able to access the database. That's a great idea for Production however it makes it very difficult to develop, debug and test applications locally. The instructions below will help you to create a tunnel towards Neptune endpoint considering you use Amazon EKS - a managed Kubernetes service from Amazon. As a side note, if you don't use EKS, the same idea of creating a tunnel can be implemented using a Bastion server . In Kubernetes we'll create a dedicated proxying pod. Prerequisites. Setting up a tunnel.

Elasticsearch CORS with basic authentication setup

This is a short "recipe" article explaining how to configure remote ElasticSearch instance to support CORS requests and basic authentication using Apache HTTP Server 2.4. Proxy To start with, we need to configure Apache to proxy requests to the Elasticsearch instance. By default, Elasticsearch is running on the port 9200: ProxyPass /elastic http://localhost:9200/ ProxyPassReverse /elastic http://localhost:9200/ Basic authentication Enabling basic authentication is easy. By default, Apache checks the user credentials against the local file which you can create using the following command: /path/to/htpasswd -c /usr/local/apache/password/.htpasswd_elasticsearch elasticsearchuser Then you'll need to use the following directives to allow only authenticated users to access your content: AuthType Basic AuthName "Elastic Server" AuthUserFile /usr/local/apache/password/.htpasswd_elasticsearch Require valid-user For more complex setups such as LDAP-based