Jump to content
We've recently updated our Privacy Statement, available here ×

jtotaf

Members
  • Posts

    11
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Everything posted by jtotaf

  1. Here you go! Please note that this comes with no guarantee of any kind either implied or explicit. The files I changed were HibernateDataAdapterService.java, SpringHibernateDataAdapterService.java, VirtualizableElementList.java and XmlaDataAdapterService.java. All the best!
  2. It turns out to be relatively easy to create a JRE 1.5 compatible version of the JasperReports 4.5.1 library. I've created the jar file if anyone is interested.
  3. Thanks Teodor for your prompt response! Could you tell me the last JasperReport release that is fully compatible with JRE 1.5. Thanks again!
  4. We've just upgraded to JasperReports 4.5.1. I'm now getting a NoSuchMethodError when trying to create an 108,000 line text report using JRSwapFileVirtualizer and exporting it using JRCsvExporter. It appears that the VirtualizableElementList class is using a binarySearch method only available in JRE 1.6. According to the Ultimate guide JRE 1.3 is all that is required. Our platform uses JRE 1.5 and cannot be upgraded at this time. Can you supply a patch or a workaround. Here is the stack trace: Exception in thread "main" java.lang.NoSuchMethodError: java.util.Arrays.binaryS earch([iIII)I at net.sf.jasperreports.engine.base.ElementsBlockList.blockIndex(Virtual izableElementList.java:711) at net.sf.jasperreports.engine.base.ElementsBlockList.get(VirtualizableE lementList.java:586) at net.sf.jasperreports.engine.base.VirtualizableElementList.get(Virtual izableElementList.java:96) at net.sf.jasperreports.engine.base.VirtualizableElementList.get(Virtual izableElementList.java:54) at net.sf.jasperreports.engine.export.JRGridLayout.createWrappers(JRGrid Layout.java:958) at net.sf.jasperreports.engine.export.JRGridLayout.<init>(JRGridLayout.j ava:143) at net.sf.jasperreports.engine.export.JRCsvExporter.exportPage(JRCsvExpo rter.java:53) at net.sf.jasperreports.engine.export.JRAbstractCsvExporter.exportReport ToWriter(JRAbstractCsvExporter.java:240) at net.sf.jasperreports.engine.export.JRAbstractCsvExporter.exportReport (JRAbstractCsvExporter.java:187) Thanks!
  5. Hi: There is no need any more to rebuild the library yourself without Javaflow. Later versions of the distribution now include a version without javaflow and a version with javaflow. john
  6. Hi! Mike I've tried IS_DETECT_CELL_TYPE but this has the down side that fields that you want to be numbers in the spreadsheet are saved as text. So rather than using IS_DETECT_CELL_TYPE, I've used IS_AUTO_DETECT_CELL_TYPE so that numbers are saved as numbers and any numeric fields that require the leading zeroes I simply prepend a "'" (single quote) which signals to Excel to format the number as text. But please note that for some reason when initially opening the spreadsheet the single quote is displayed until I click on the cell and its text in the toolbar. Mike or Lucian, in a forum item I posted Dec 7/06 I explain that I'm getting a 'cannot resolve symbol' error when setting the IS_DETECT_CELL_TYPE (to set IS_DETECT_CELL_TYPE as described above I had to change the defaults in the code and recompile). Any ideas on what I'm doing wrong. Thanks, john
  7. Hi! I'm getting a 'cannot resolve symbol' error when trying to set the XLS exporter parameter IS_DETECT_CELL_TYPE. In contrast there is no error when setting the IS_AUTO_DETECT_CELL_TYPE. I'm probably missing something obvious but I don't see why the compiler can resolve one and not the other. Appreciate any suggestions. Here are the details: jasperreports-1.2.7, java 1.4 Error: Code:javac: [javac] cannot resolve symbol [javac] symbol : variable IS_DETECT_CELL_TYPE [javac] location: class net.sf.jasperreports.engine.export.JRXlsExporterParameter [javac] exporter.setParameter(JRXlsExporterParameter.IS_DETECT_CELL_TYPE, new Boolean(true)); [javac] ^ [javac] 1 error Code snippet: Code:[code]import java.io.*; import java.sql.Connection; import java.sql.DriverManager; import java.sql.PreparedStatement; import java.sql.ResultSet; import java.sql.SQLException; import java.util.*; import java.text.SimpleDateFormat; import java.text.DecimalFormat; import net.sf.jasperreports.engine.JRException; import net.sf.jasperreports.engine.JRExporterParameter; import net.sf.jasperreports.engine.JasperExportManager; import net.sf.jasperreports.engine.JasperFillManager; import net.sf.jasperreports.engine.JasperPrint; import net.sf.jasperreports.engine.util.JRLoader; import net.sf.jasperreports.engine.export.JRCsvExporterParameter; import net.sf.jasperreports.engine.export.JRTextExporter; import net.sf.jasperreports.engine.export.JRTextExporterParameter; import net.sf.jasperreports.engine.export.JRXlsExporter; import net.sf.jasperreports.engine.export.JRXlsExporterParameter; import org.apache.log4j.Logger; import org.apache.log4j.PropertyConfigurator; . . . File sourceFile = new File(curName + ".jprint"«»); JasperPrint jasperPrint = (JasperPrint)JRLoader.loadObject(sourceFile); File destFile = new File(curName + ".xls"«»); JRXlsExporter exporter = new JRXlsExporter(); exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint); exporter.setParameter(JRExporterParameter.OUTPUT_FILE_NAME, destFile.toString()); exporter.setParameter(JRXlsExporterParameter.IS_DETECT_CELL_TYPE, new Boolean(true)); exporter.setParameter(JRXlsExporterParameter.IS_AUTO_DETECT_CELL_TYPE, new Boolean(false)); exporter.setParameter(JRXlsExporterParameter.IS_REMOVE_EMPTY_SPACE_BETWEEN_ROWS, new Boolean(true)); exporter.exportReport(); Thanks, john
  8. Thanks again Lucian. Just one last point - I'd like to find out more about how to use javaflow continuations in jasperreports but when a try to attach to the URL you gave I get the message Artifact: Only Group Members Can View Private ArtifactTypes even when I've logged on. Can I get access to this or is there another URL to use? Thanks, john
  9. I removed javaflow as you explained and rebuilt jasperreports-1.2.5.jar on Windows Xp with j2sdk1.4.2_11. Copied this to AS400 and found that reports now run fine on AS400. Many thanks to Lucian and Teodor for your help! Is there any significant functionality that will be lost without javaflow? Would you recommended that we continue to use the version with javaflow on the platforms where it works (i.e. Windows, AIX)?
  10. Thanks Teodor: I've confirmed that the Javaflow jar is in the classpath. I also tried setting the os400.verify.checks.disable property to 'bypass access checks for local classes' and 'suppress NoClassDefFoundError during early load'. But I'm still getting the error: java.lang.VerifyError: net/sf/jasperreports/engine/fill/JRBaseFiller 0000 0000 at java.lang.Throwable.<init>(Throwable.java:195) at java.lang.Error.<init>(Error.java:49) at java.lang.VerifyError.<init>(VerifyError.java:34) at net.sf.jasperreports.engine.fill.JRFiller.fillReport(JRFiller.java:57) at net.sf.jasperreports.engine.JasperFillManager.fillReportToFile(JasperFillManager.java:147) at GenerateReport.generate(GenerateReport.java:707) at GenerateReport.main(GenerateReport.java:241) (GenerateReport is the main). It's only the AS400 we're having trouble with. I've successfully run Jasperreports 1.2.3 on Windows Xp 5.1 and AIX 5.1. john
  11. Hi! Running jasperreports 1.2.3 on AS400 with JVM V5R3M0 and JDK 1.4.2 gives error: java.lang.VerifyError: net/sf/jasperreports/engine/fill/JRBaseFiller 0000 0000 The headless AWT toolkit environment is being used. We have NOT had this problem with jasperreports 1.0.3. I'd like to get 1.2.3 or later running to use a new feature (Evaluation Time auto). Appreciate your help. john
×
×
  • Create New...