shivasakthi18 / alfresco-business-reporting

Automatically exported from code.google.com/p/alfresco-business-reporting
0 stars 0 forks source link

Error on scripts to execute all reports #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Follow documentation steps on Alfresco 4.0d
2. Execute executeAllReport.js using Alfresco Command Servlet

What is the expected output? What do you see instead?
Execution of sample report using JasperReport at least
Obtain instead the following error:

Caused by: org.alfresco.error.AlfrescoRuntimeException: 00140017 
org.codehaus.groovy.control.CompilationUnit$ClassgenCallback.call(Lorg/objectweb
/asm/ClassVisitor;Lorg/codehaus/groovy/ast/ClassNode;)V
    at org.alfresco.repo.jscript.RhinoScriptProcessor.executeScriptImpl(RhinoScriptProcessor.java:499)
    at org.alfresco.repo.jscript.RhinoScriptProcessor.execute(RhinoScriptProcessor.java:191)
    ... 22 more
Caused by: java.lang.AbstractMethodError: 
org.codehaus.groovy.control.CompilationUnit$ClassgenCallback.call(Lorg/objectweb
/asm/ClassVisitor;Lorg/codehaus/groovy/ast/ClassNode;)V

What version of the product are you using? On what operating system?
Alfresco 4.0d / MySQL 5.5.21 on Windows 2008 Server

Please provide any additional information below.

I've include all standard libraries of zip file 
unzip-into-webapps-alfresco-lib-0.6.5 (skipping xpp3-1.1.3_8.jar and 
xmlsec-1.4.1.jar that already existed). Probably the problem is related to some 
jar dependencies but I've used only standard alfresco jars

Original issue reported on code.google.com by vincenzo...@gmail.com on 14 Jan 2013 at 5:38

Attachments:

GoogleCodeExporter commented 8 years ago
Seems that the problem is solved replacing the jasperreport libraries

Thanks
Vincenzo

Original comment by vincenzo...@gmail.com on 25 Jan 2013 at 10:38

Attachments:

GoogleCodeExporter commented 8 years ago
Thanks for the list of libraries, and sharing the solution to the issue with us!

I am almost convinced to drop JasperReports from the supported stack. They do 
not have a zip-like structure for sub reports. They expect the reports on 
relative path's of the main report instead. That is a pain in extracting the 
reports to a temporary location for execution, because what reports to retrieve 
from Alfresco as associated sub reports?
Next to that I don;t have the time to validate all options currently avaiable 
for Pentaho against JasperReports too. That is the pragmatic approach.

I guess the issue originated from a newer version JasperReports of your reports 
(versus an old supported version in the module). The new list is useful for 
those that continue to use JasperReports...

Cheers!

Original comment by tjarda.p...@incentro.com on 13 Mar 2013 at 9:54

GoogleCodeExporter commented 8 years ago
Since no response, I assume this issue can be closed... Please feel free to 
re-open if needed...

Tjarda

Original comment by tjarda.p...@incentro.com on 6 Apr 2014 at 10:23