When exporting the JasperReports Server repository content using the command line utility, the user must make sure that the utility version used for the export matches the repository version. If a different version is used, they may run into 'Cannot instantiate abstract class or interface' error.
If debug logging (refer to http://community.jaspersoft.com/wiki/getting-cannot-instantiate-abstract-class-or-interface-error-when-running-js-export) indicates the problem relates to an ad hoc view in the repository. But, upon further examination, the repository does not reveal any problem with the view, then most likely the user is using a pre v4.7.0 export utility to run the export against a post v4.7.0 repository data source. Since the Ad Hoc view was introduced in 4.7.0, prior versions of the product will not recognize the resource type nor be able to export it properly.
One simple test to find out whether an import utility is pre or post v4.7.0 is to review the date and time stamp of the utility module under buildomatic directory. If the time stamp is before 6/29/2012 when 4.7.0 release package was built, then it is a pre 4.7.0 utility.
TTC-20141127-55306
Recommended Comments
There are no comments to display.