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

mdrg

Members
  • Posts

    36
  • Joined

  • Last visited

mdrg'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. Hello, I reported this as a concern about the default handling of NullPointerException a while back, but unfortunately it got no attention. I'd like to know what's the reason for this behavior, and maybe if it could be made configurable in the future. I'm copying the bug description here: Any exception that may happen during field evaluation (either direct field expression or scriptlet method) always propagate up the stack, aborting the report, except NullPointerException. It's obvious that all values should be tested for null, but the programmer may forget to do all the needed tests sometimes, or the data which was expected to exist is missing. Such situations that cause NPE's get silently evaluated to null. I don't know the reason behind this explicit exception swallow, but I'd like my reports to abort on any exception that may arise, including NPE's, and I dare to say that's what most programmers would expect (at least the Java ones, that may frequently deal with scriptlets, where such exceptions are far more likely). I'm currently running my local report tests on custom JasperReports 4.0.0 build with NPE catch blocks removed, no issues. I suggest the creation of new report option (probably report-wide), like 'When NullPointerException on evaluation', with values 'Evaluate to null' (default, to keep backward compatibility) and 'Propagate'. Bug URL, with sample report: http://jasperforge.org/projects/jasperreports/tracker/view.php?id=5203 Thanks!
  2. I missed this property, thanks! Someone with thoughts on my second question, still welcome ;-)
  3. If I got this correctly, just use 'remove line when blank' on the text field.
  4. Try adding the JDT compiler to your client machines. Its the recommended compiler according to the requirements: http://jasperforge.org/projects/jasperreports
  5. You already asked it : http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=86480 If your set of possible column variations is small and predictable enough, you can use multiple subreports and choose which one you wish to display. Otherwise try DynamicJasper.
  6. Please, anybody can share some light with me on this? Thanks!
  7. Try DynamicJasper: http://dynamicjasper.com/ It is built upon JasperReports and provide ways to define reports with dynamic layouts.
  8. This is not related to Jasper. You should try some Java programming community.
  9. I believe that grouping is exactly what you need to perform this kind of task. Read a bit about "groups" functionality, that's probably what you need.
  10. Set the text field markup to "styled" and use <style isBold="true"></style> around the text you wish to be bold. Where to put this tag is up to you, according to your requirements and needs. You probably can do it easily with String manipulation methods, as long as you can locate the text you want to be bold. I suggest you do this on a Scriptet, so you can use all of Java String manipulation methods and classes. Post Edited by mdrg at 04/15/2011 11:51
  11. You may join them in a single document creating a "master" report and adding the multiple jasper files you have as subreports. Give it a try.
  12. Why don't you do the opposite? Query the data in your application and use it to create the table. If the user requets a report, send the same data using a bean collection/array datasource to populate the report.
  13. I'm still hoping to get an answer. Thanks!
  14. Use 'ignore pagination' option on your reports and you'll get a report with no pages, as a single, very tall page.
×
×
  • Create New...