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

europe72

Members
  • Posts

    30
  • Joined

  • Last visited

europe72's Achievements

Contributor

Contributor (5/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges

0

Reputation

  1. Hello, Thank you for your reply. I looked at the screencast, that is an excellent solution, and is much appreciated!
  2. Changed Assigned User from @User_306070 to @anonymous Hello, thank you for your reply.If this is the case, which xsd would the saved source need to conform to upon saving from the source tab? Latest, or the selected legacy jrxml version?Also, what happens when I preview an unsaved JRXML file? Does that trigger the compatibility check? Should it?Thank you
  3. Hello and thank you for your reply. I'm not sure what type of file you would want to test exactly? The jrxml files are well formed and work in iReport when I include my scriptlet jars in the classpath in preferences. The only other file might be the .project or .classpath, and both of those look right to me based on my experience using Eclipse to develop Java. Please advise.
  4. I'm using 1.0.8, and I have the same issue - I am unable to get my scriptlet jar classes to resolve to a type. My project has a Jasper nature, and a java nature. I have the Jasper builder and the Java builder. I have a .classpath file, and in it is an entry for the jar files. This does not work, and all of my reports that utilize any of my custom Scriptlets are littered with errors. Any advice would be appreciated heading back to iReport...
  5. Hello, I'm currently in the process of coding a Servlet, which creates a JasperPrint object, and subsequently exports it via JRExporter. Below is a snippet of code from that Servlet. I was attempting to create a File obj from the OUTPUT_FILE, however OUTPUT_FILE is null even after exportReport() is called. Should it be? Code:... ServletOutputStream os = response.getOutputStream(); exp.setParameter(JRExporterParameter.CHARACTER_ENCODING, p.get("encoding")); exp.setParameter(JRExporterParameter.JASPER_PRINT, jp); exp.setParameter(JRExporterParameter.OUTPUT_STREAM, os); try { exp.exportReport(); } catch (JRException e) { response.sendError( HttpServletResponse.SC_INTERNAL_SERVER_ERROR, e.getLocalizedMessage()); e.printStackTrace(); } File f = (File) exp .getParameter(JRExporterParameter.OUTPUT_FILE); response.setContentLength((int) f.length()); os.flush(); os.close();...
  6. "but from my point of view it doesn't correspond to the problem at all. Heap is getting full while filling the report, not while exporting" In the context of this thread you are absolutely correct, however the xls libs themselves have their own problems with memory. But perhaps it doesn't pay to muddy up this thread with those issues (as they are already addressed elsewhere). Anyhow, a way to use a virtualizer on a report where ignore pagination bit is flipped to true will hopefully trickle into the codebase at some point in the future.
  7. I'm very eager to see this information and appreciate the reply. I'll check back after the conference!
  8. I'd also be interested if there are any good workarounds. The heap issues with Excel output are a huge problem for me. I use POI; can't use JExcel/JExcel's tmp file during write option (which is the only mem mgmt I have found for non-paginated output with an excel lib). I'm considering an investment in aspose.cells. I just can't get memory under control in non-paginated, non-virtualized excel any other way.
  9. JFYI, a post with the same end goal as yours (improving/optimizing excel output performance) http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=83270
  10. Hello, I noticed that when the program details were posted for the conference that there was the following session made available: "Data-centric Excel Output" The description of this session is: "The Excel output format is one of the most frequently created with Jaspersoft-powered solutions. Given its nature, however, most users want to be able to interact with these generated Excel files, or want to feed data in these files into other systems for further processing. In these cases, it’s important to bypass the pixel-perfect aspects of JasperReports (because even Excel output can be formatted—but in this case, we just want data). This session shows you how to achieve this, using a series of export parameters and configuration properties." I'm very much interested in this content, but will not be attending the conference, and am wondering how the content might be made available either before or after the conference to non-attending community members. I'd be glad to pay for the content in the form of an e-learning solution, or a soft copy of the slides etc. Sounds like the conference is really going to be pretty exciting; with some great material. If I didn't live all the way across the country, I'd certainly be there! Thanks and please advise.
  11. And I just saw this, which is almost certainly in context: http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=59035
  12. Hello, I've been using JasperReports for a few years now. In that time, I have learned the product fairly well, and come to respect its ability to produce both simple and complicated reports with a fair amount of grace. I've also learned however that memory consumption is often less than desirable and the speed of rendering is quite poor. Specifically reports that are rendered to continuous media (eg. excel) can take [what I personally believe to be] far too much time to finally output. As an example of this, I have one report which is about 20 columns and 7K rows. The report is setup in such a way where there is a container report with a report title and column headers, while the data comes from a subreport. Pagination is off (otherwise I get blank rows in my excel output where pages would have occurred), and as a result I can't use a virtualizer (not that virtualizers speed up report generation anyway, but they do help with memory footprint/heap exceptions). None of the fields are formatted in any way, and the query is quite fast to run. Despite this, I have experienced (when I don't hit a heap exception) output times upwards of 10 minutes, and I am struggling to understand why the performance is so bad. When I monitor the thread running JasperReports, and when I monitor the network usage and server resources I see that Java is taking a *huge* amount of memory, and is basically pegging out the CPU. Network tools show very little traffic between my client and the server apart from the initial request to run the report, then network spike again when the report is handed to client. The network is not congested in the least, and even when running locally in a development environment where jasperreports and the MySQL 5 server are on the same machine, I experience similar performance. What can I do to improve performance? Thanks PS: Performance is poor even if I am testing in iReport. I do use a custom implementation, but iReport of course does not use that.
  13. On further inspection the sales office subreport itself is only printed for the first invoice item. What would cause the subreport (in this scenario) to only print for one - the first - detail row?
  14. FYI Vote case for Note: 0009405's proposed solution.
×
×
  • Create New...