Jasper Reports

Thread view:

JScoobyCed - 21 Mar 2006 10:07 GMT

Hi,

We are just discovering Jasper Reports and it looks such a great API!
Is there any "do not do" that we have to be careful if we want to
implement with Tomcat + Apache + AQL Server?
Many thanks,

Signature

JSC

Reply to this Message

Ingo R. Homann - 21 Mar 2006 10:46 GMT

Hi JScoobyCed,

> Hi,
>
> We are just discovering Jasper Reports and it looks such a great
> API! Is there any "do not do" that we have to be careful if we want to
> implement with Tomcat + Apache + AQL Server?
> Many thanks,

I have worked with JasperReports (and iReports) using Tomcat and it
worked fine!

On the other hand, I prefer directly using iText meanwhile, which is
much more flexible (JasperReports is based on iText).

Ciao,
Ingo

Reply to this Message

JScoobyCed - 21 Mar 2006 11:46 GMT

> I have worked with JasperReports (and iReports) using Tomcat and it
> worked fine!
[quoted text clipped - 4 lines]
> Ciao,
> Ingo

Thanks for the info. We are actually going to generate tables of data
(Excel like stuff, but with the option to save as PDF). If Jasper does
the trick it will save us time. But for basic pages, I agree on using
iText directly (which is the API that made us discover Jasper :) ).

Signature

JSC

Reply to this Message

Ingo R. Homann - 21 Mar 2006 13:23 GMT

Hi,

>> I have worked with JasperReports (and iReports) using Tomcat and it
>> worked fine!
[quoted text clipped - 8 lines]
> (Excel like stuff, but with the option to save as PDF). If Jasper does
> the trick it will save us time.

I think, it is a good choice, then!

> But for basic pages, I agree on using
> iText directly (which is the API that made us discover Jasper :) ).

Interesting - I think, the opposite is true: I think, for simple, basic
Documents (e.g. a simple Table with some headers), JasperReports is
perfect - but when you want to do "advanced" things (nested tables, much
texts, variable number of columns, ...), I think, iText is more flexible
and more comfortable.

Ciao,
Ingo

Reply to this Message

JScoobyCed - 22 Mar 2006 02:35 GMT

> Interesting - I think, the opposite is true: I think, for simple, basic
> Documents (e.g. a simple Table with some headers), JasperReports is
> perfect - but when you want to do "advanced" things (nested tables, much
> texts, variable number of columns, ...), I think, iText is more flexible
> and more comfortable.

In our case, "basic things" are labels and stickers. Take an A4 format
paper with 8x4 stickers, 5mm border on the top and bottom. We have
triied to do it in HTML (CSS and tables...). That was a nightmare, as
every client had different page format settings and browsers. We had to
adjust the borders, cellspacing, paper format... for each and very
client. Or if they purchased a new printer, we needed to adjust again.
With a PDF (or RTF or XLS) document, we are sure we will have to write
the code once.

Cheers,

Signature

JSC

Reply to this Message

Jasper Reports

Free Magazines