Jump to content

allend

Members
  • Posts

    2
  • Joined

  • Last visited

allend's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. I'm not certain whether or not this will help, but there is a constant in the JRXmlConstants class called JASPERREPORT_DTD that contains a string for the location of the DTD file in the jar. So, if you can pinpoint the place where the DTD is referenced by its sourceforge URL, you at least know what to replace it with (in Java code, anyway). Hope that's somewhat useful. ~DVA
  2. Hi, all. I'm new to Jasper, but am working on a proof-of-concept for augmenting/replacing our program's current in-house reports system. Anyway, one problem that I've found is that our old reports system included search info. in the same XML as the formatting, e.g. "here are the fields the user can search on, and then format the output of the query thusly". JRXML only does the formatting. Our users aren't tech-savvy enough to compose their own SQL, so we have a search dialogue, which needs that info. (Can't change that, for back-compatibility reasons) I could have two files for each report, one format and one search. Not entirely illogical, but tedious--we write new reports frequently, so if I can avoid the proliferation of files, I'd to. Instead, could I create a new type, extending the JRXML DTD via importing it with !ENTITY in my custom DTD? How would I go about parsing that? I wanted to extend the parser that Jasper uses, but it looks like that's hidden behind the JasperCompileManager. I was wondering if anyone had any suggestions on how I might go about doing this, or alterntative approach I could use. It's a general question, I know, but I'll accept correspondingly general answers. :)
×
×
  • Create New...