JasperReports Disappoints



Email    print   
December 15, 2005 —  (Page 1 of 2)
So, you’ve just bought a used car. You put the key in the ignition, and nothing happens. You turn to the salesman, who looks you in the eye and says, “Oh! you wanted an engine with that car! That’ll cost you extra.” This same story applies to a lot of free software. You can download it for free, but when it comes to learning how to use it, or getting all of the features that you really require, it will cost you extra.

I’ve been spending the past few days working with JasperReports (jasperreports.sourceforge.net). This package is a popular report generator that started out as an open-source project and has now transmogrified into a company called JasperSoft.

The problem is that JasperReports itself is an amateurish piece of work with an unwieldy install process and lousy documentation. You must download the library from SourceForge, but like a lot of open-source software, you must also manually find and load other libraries to satisfy internal dependencies, then you also have to install ant, and run various ant scripts to compile the thing. The online documentation is the typical disorganized collection of “sample apps” with an inadequate overview thrown in as an afterthought. In the you-want-an-engine-with-that-car department, the author of the library will sell you a US$50 book (“The JasperReports Ultimate Guide”) that comprises the real documentation. Or so it would seem.

Unfortunately, much of the “Ultimate Guide” itself is made up of sequences of words that begin with a capital letter and end with a period, but which don’t form a sentence in the English language. For example: “The initial report templates have to be compiled into a more digestible form before being used for filling with data.” And “To use a report virtualizer is very simple. It is only about supplying an instance of the net.sf.jasperreports.engine. JRVirtualizer interface as the value for the built-in parameter called REPORT_VIRTUALIZER when filling the report.” The documentation is filled with programmers’ conceits, like using an XML DTD to describe syntax—a format that virtually nobody understands, though it does prove that the author is more of an uber geek than you. To make things more confusing, the documentation literally has no examples in it.




Pages 1 2 


Share this link: http://sdt.bz/29024
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE

 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb