iReport 0.3.2 released!

[2004 IR Help]

By: Giulio Toffoli - gt78

iReport 0.3.2 released!

2004-07-15 13:21

 

The iReport Team is pleased to announce the new iReport release: 0.3.2.

 

See details on iReport 0.3.2 What's new? page (http://ireport.sourceforge.net/relnotes0.3.2.html)

 

 

iReport is a visual report designer for JasperReports written in 100% pure java. You can manage charts, images, subreports,...

Data can be retrived using JDBC, TableModels, JavaBeans, XML,...It supports output in PDF,XML,XLS,CSV,HTML,Java2D, TXT...

 

0.3.2 version contains:

 

- New Datasource connections (CSV, XML, Extende Bean)

- Fixed problems with Wizard

- Support for read-only files

- Support for MaxOSX and fixed problems on Linux

- New Pattern editor

- New Collision Detection feature

- New Element band switching feature

- Short Cut keys for Alignments

- Copy and paste field style

- Key names for elements

- Fixed Zoom

- New Languages:

Dutch by Robert Lamping

Japanese by Ezo

Pole by Malgorzata

Romanian by Alexandru Carstoiu

Chinese Taiwan (Traditional) by Primo Chen

Chinese (Simplify) by Primo Chen

Chinese (Traditional) by Primo Chen

And much more...

 

Download it at: http://sourceforge.net/project/showfiles.php?group_id=64348

 

Thanks

 

the iReport Team

http://ireport.sf.net

 

 

 

 

 

 

By: C-Box - c-box

RE: iReport 0.3.2 released!

2004-07-15 23:13

Hi Giulio,

 

first a BIG THANKS for the new release... the new features sounds great... but I get the "Exception in thread "main" java.lang.UnsupportedClassVersionError: it/businesslogic/ireport/gui/MainFrame (Unsupported major.minor version 49.0)"

like Kap1000 with "j2sdk1.4.2_03" ... do I HAVE TO use 1.5 or is there also a way to use the current more stable java-version?

 

 

greetings from Germany

C-Box

 

 

 

 

By: supportsib - supportsib

RE: iReport 0.3.2 released!

2004-07-17 02:24

Cannot start?

 

 

 

 

By: Giulio Toffoli - gt78

RE: iReport 0.3.2 released!

2004-07-17 14:42

now it's all ok.

Retry to download ireport.

 

Ciao!

 

Giulio

 

 

 

 

By: C-Box - c-box

RE: iReport 0.3.2 released!

2004-07-19 00:30

Good morning Guilio,

 

I've downloaded today the new 0.3.2 (compiled 17.07.2004 00:23)... now I can start with j2sdk1.4.2_03 but my old reports doesn't get compiled yet....

 

just NOTHING HAPPENS after click on the compile button.... no error... no log... just nothing...

 

new reports work fine.

 

any idea?

C-Box

 

 

 

 

By: C-Box - c-box

RE: iReport 0.3.2 released!

2004-07-19 01:21

Me again :-)

 

I figured out, that just my old (designed with 0.3.1) reports that contains SUBREPORTS can't get compiled with IReport 0.3.2 (saturday release).... the other ones (designed also with 0.3.1 but have NO SubReports) can get compiled......

 

Did you changed anything on the compilation-routine concerning SubReports??????

 

I have following statements: .....

<dataSourceExpression><![CDATA[$P{DataContainer}.getFilterableDataSource("SRPositionen","Id",$F{Id})]]></dataSourceExpression>

<subreportExpression class="dori.jasper.engine.JasperReport"><![CDATA[$P{DataContainer}.getSRPosDBaustein()]]></subreportExpression>

 

So it's NO DIRECT parameter and also NO FILE that points to the SubReport.

 

The class where the methods are within, is set in the CLASSPATH, if not the exception "Class not found" appears.. so it CAN'T be a class-path-problem.

 

C-Box

 

 

 

 

By: Giulio Toffoli - gt78

RE: iReport 0.3.2 released!

2004-07-19 01:42

I don't have this problem.

 

Try to compile a simple void report with a subreport only.

 

Let me know.

 

Giulio

 

 

 

 

By: C-Box - c-box

RE: iReport 0.3.2 released!

2004-07-19 05:30

OK, I found the problem...

 

I had included a "import" Statement in my new class (that returns the SubReport) what actually is not needed anylonger and all lines are commented out... but somehow JasperCompileMangager needs all the import-classes to be on classpath... but that Import-Statement-class wasn't on classpath yet.

 

It was every old report of mine that contained a SubReport, so just the presence of that parameter was enough to let invoke that strange behavior. If I changed the parameter class-type to java.lang.String everything works fine.

 

I just wonder, why no exception is fired?!?!?

 

C-Box