DocumentBurster – Report Delivery. Report Distribution. Report Bursting. Email & FTP

DocumentBurster | Free software downloads at SourceForge.net

DynamicReports: reporting library based on JasperReports

DynamicReports - Free and open source Java reporting tool

iReport vs. version control

Tried to include a JRXML string variable with "$Revision$" as initial expression. It's impossible to have such a string, as "$" is expected to start something JRXML specific like a field, a variable (itself!!), a paramater. And including a backslash "\" destroys the idea resp. the effect.
So: no RCS / CVS / subversion strings in JRXML. Alright within XML comments they work. But then: you never know for sure, what iReport does with your XML comments. With any future release they may decide to remove XML comments. Then you are pissed.

JasperForge > Jaspersoft Studio Forum(s)

JasperForge > Jaspersoft Studio Forums

The Open Book on BI: Finally . . . Reporting for Eclipse!

The Open Book on BI: Finally . . . Reporting for Eclipse!

Jaspersoft joins Eclipse Foundation - The H Open Source: News and Features

Jaspersoft joins Eclipse Foundation - The H Open Source: News and Features

Jaspersoft Studio News

JasperForge > Jaspersoft Studio News

Jaspersoft Studio works within Eclipse just like iReport works within NetBeans.

Jaspersoft Studio is a new, free, open source report designer for JasperReports. A full rewrite of iReport on top of the Eclipse platform.

jasperforge.org/projects/ireport/wiki

Wiki

how to connect iReport to the database, that comes with a JasperServer (installation)?

This is the JDBC-URL (replace "JASPERSERVER" appropriately!):


jdbc:mysql://JASPERSERVER/sugarcrm


And the default credentials are: jasperdb/password.

Next issue: dealing with "repo:", a reference to the resource repository on the JasperServer …

a Google Group on "JasperReport and iReport"

JasperReport and iReport - Google Groups

It's a private group, i.e. you can't easily find something in them from outside (YKWIM).

iReport: Java Heap Space problems

JasperForge > iReport Forums

This thread discusses, how to solve this problem at filling and also at export time (JasperReports jargon).

Filling time configuration:

• ... > iReport > Compilation and execution > Execution options > [_] Limit the number of records (=?!= REPORT_MAX_COUNT -> the iReport UG, 6.2.3)
• ... > iReport > Compilation and execution > Execution options > [_] Use virtualizer
• ... > iReport > Compilation and execution > Virtualizer; apress's TDG to iReport treats the Large Report problem (a little) in chapter 18 "Solutions to Common Problems": "... Using Report Virtualizer".

Export time configuration:

The above thread discusses how to pass a "java -XmxN" parameter via iReport. (This is good for manipulating the size of the memory allocation pool.)

Traditionally that was to be specified on the iReport command line.
The modern way to achieve this is through

/etc/ireport.conf

how do I point my iReport to a JasperServer?

On OS X: Window > JasperReports Server Repository.
In the Repository Navigator there is an icon with a "+" (white on green) with the hint text "Add new server".

an INCOMPLETE story from my "PDF to JasperReports" migration project

My "current" (as of 2011-01) project is actually rather interesting and challenging and well-paying,
but it's only going to last for no longer than 2 months, I assume.

From my customer's point of view this migration project must be horror.

I don't really know, how serious "they" were, when they determined, that this would be a 3-months project.

Migrating 98% of the documents from PDF to JasperReport's "JRXML"

  http://en.wikipedia.org/wiki/JasperReports#JRXML

will take like 6 months (I started in December).
But the remaining 2% of the documents may take another 3 to 6 months.

If they don't complete that project (I mean true 100% of the documents, that need to get migrated),
they cannot abandon the old software,
which was one of the main goals initially.

They had no realistic concept for migrating all these documents,
they even had no realistic approach of analyzing all the PDF documents.
We are talking about many hundreds of PDF documents resp. pages with form fields,
and these form fields are really rather "delicate" details.

The usual way to work on PDF form fields
is to load the file into Acrobat Pro and to display the form fields.
You can "obviously" create a hard copy for each page,
but that's tedious and you still don't have hold of all the "more atomar details" of PDF form fields.

There was no software available for easy "batch-way" dealing with PDF forms.
I created something myself around a PDF library from perl's CPAN ("CAM::PDF").
Oh, wonderful CPAN!!!
In the meantime I contacted the developer of that PDF library,
because I needed more details for PDF document objects, such as the page number of a form field,
and "of course" he helped me out.
I was so happy.
Initially the page number was only "nice to have",
as 99.5% of the documents, that I had dealt with so far, were 1-page only.

In the meantime I found out, I would have to deal with like 200 multi-page documents,
so it was a serious necessity to be able to extract the number of the page the form-fields are located on.

When I decided to contact the developer of CAM::PDF, I was already close to despair,
and I was overly happy, when we had gotten that feature implemented within a couple of days, with just a few e-mails in both directions.