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

drlaz

Members
  • Posts

    23
  • Joined

  • Last visited

drlaz's Achievements

Explorer

Explorer (4/14)

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

Recent Badges

0

Reputation

  1. Right now I am working from iReport 3.6 and Jasper 3.6. My report doesn't pull in that many records, about 800. Two of the database fields are text svg, all different. These convert back into graphics OK, and the fill appears to work. I am using the Swap virtualizer set for 100,000 blocks. PDF export hangs after about 200 records. If I have only a few records, the export works perfectly. Any ideas how to get the report to stream to export successfully?
  2. The second time this happened to me I tried harder to find the solution, and it appears to be a classpath problem!? I saw that some of the jasper jars were duplicated (in different directories) in the classpath. In my case, one set was in an iReport directory and another was in a JasperReport directory. When I examined the REPORT_SCRIPLETs variable in a watch window, it had multiple copies of my scriptlet. Somehow the internal mechanism to find scriptlets doesn't look at only the package/classname of the scriptlet but of jar calling it, or some other weirdness. In other words, there must be a full classpath search for anything capable of loading the scriptlet instead of stopping at the first match as you would expect from a classpath search. After deleting the duplicates from the classpath, all worked well.
  3. I have overrides of beforeGroupInit, afterGroupInit, and afterDetailEval. They are all called twice as often as they should be; e.g., twice for each record for the afterDetailEval. Any ideas? My scriptlet's variables are, obviously, getting munged. By the way, is the GroupFooter calculated after afterGroupInit?
  4. Make sure that the scriptlet is in your classpath (under Preferences--this is global to iReport, not just individual report). Then in the Report Properties, put this fully qualified name of the scriptlet. like com.me.mypackage.MyScriptlet. Remember that this should be relative to the classpath entry.
  5. The basic idea is that you want to apply a text style to that field, and instead you are telling iReport that the contents of the field contain style information. You want to uncheck Styled Text and put the name of your style in the Style field that in 3.0.0 is just above the "Print When Expression" in the Properties panel.
  6. It doesn't seem to matter which I click on first, which is how Classic iReport did it. Like toast falling buttered side down, iReport consistently moves the object that is where I wanted it and fixes the object I wish to adjust.
  7. Unless you are using Java 6, to use the | and || operators you will have to make sure that you are using booleans and not Booleans. Once that is straight you should be OK. It's a rather obscure point of Java, but I believe you CAN use | instead of || but they behave differently. | is NOT a short-circuit operator; it will evaluate both operands even if the first one is true.
  8. You do not want to use the Markup/Style option in Properties, which I think you have. Reset that to the default 'none' Instead set the style property (right below Opaque) to "test", which should appear in the Dropdown. Styled markup means there will be escape sequences in the string to be honored as format controls. HTH.
  9. Another method. Declare an array in a Scriptlet, then reference the appropriate index
  10. In the standalone version, it was possible to fine tune export options. I can't find equivalent functionality in the new, netbeans version. By the way, am I the only person who finds all of the non-iReport related Options and Plugins somewhere between confusing and amateurish?
  11. If I just put the name of the executable (e.g., /usr/bin/firefox) in the text field, the filename sent to the external program is garbled.It looks like some problem escaping (or not escaping) quotation marks.
  12. To make life easier for the next poor (bloke) who gets stuck on this. JasperReports' BatikRenderer needs height and width attributes in the <svg> tag, or it gets unhappy. (Firefox, Inkscape, Mac Preview, etc. seem to handle the absence of these elements with an intelligent default or some other lenient workaround.) The line of code below must be inserted into the code that generates the SVG, in my case from a JFreeChart. Code: Post Edited by A Lazarus at 01/14/09 18:41
  13. Plan: store SVG of chart in database. Retrieve as part of a report. To simplify testing, I am streaming the svg to a file instead of the database. (I did it with the database, too, but there seem to be some issues with the ByteOrderMarker using ByteArrayOutputStreams so I used a file instead.) iReport doesn't give any error messages, but it only displays a gray rectangle. Then I opened the file in Inkscape. Opened fine. And did Save A Copy as a "plain SVG" instead of "Inkscape SVG". Jasper displayed the svg of the second file just fine. What is in the original svg that is killing the BatikRenderer?? Code: Post Edited by A Lazarus at 01/14/09 19:04
  14. I have a similar problem (except I am not getting the chart either). With your pdf, I get the red background in Evince but it is OK in Acrobat Reader (Linux platform). Some transparency setting? Go figure??
×
×
  • Create New...