Problems using custom classes in JasperReports/osgi

Description

I don't think this classifies as a bug but I think users would see it as a bug. This particular problem may occur when migrating from ADempiere to iDempiere if Jasper Reports with custom classes are used, for instance if a bean collection is used to generate a report.

In Adempiere all classes are available to all so to say. I have a plugin that depends on JasperReports. The plugin generates reports using beans of classes org.compiere.model.* and also from own custom classes. I suspect this is not an uncommon scenario.

When the JasperReports plugin is called it can't see these classes since the org.adempiere.report.jasper.library doesn't import the packages where the beans reside.

Do you know if there exists a dynamic way of importing classes to a plugin in osgi? I think that would be the best solution to this.

What I did to temporarily solve my particular problem was to import the needed packages into org.adempiere.report.jasper.library. That's a very custom solution so it would be good with a more general solution.

Any ideas?

Environment

None

Status

Assignee

Heng Sin Low

Reporter

Daniel Tamm

Labels

Tested By

None

Components

Affects versions

Due date

2012/08/31

Priority

Minor
Configure