Home >> All >> jbreport >> [ util Javadoc ]

• jbreport.util: Javadoc index of package jbreport.util.


Package Samples:

• jbreport.util

Classes:

• Stack: This provides for the semantics of a stack. By default it uses a java.util.ArrayList for management, but this can be changed by passing the appropriate java.util.List instance to the alternate constructor. This is otherwise known as a FILO (First in, last out) list. The existing stack from the java.util.* package was not used, as it is extended from the Vector class, which is fully synchronized. This is not a behaviour that is needed by default. IMHO. We do provide for all of the methods in the java.util.Stack class tho'.
• MemoryTrack: This will create a thread that will monitor the state of the memory usage of this application. It is envisioned that this will eventually be tied to both the naming and messaging services. This class is made into a singleton, as we can only track memory for the entire VM, so making it any more fine-grained would be pointless. We should track trends in the memory, such as memory delta per time both over short, and longer periods of time.
• BreakEventListener: This interface defines the methods that should be implemented by any class that needs to be notified of break events during the loadData phase of report creation. This enables classes to do any splitting of pages, printing of headers, etc. that might be required during the report generation.
• ReportBreak: A ReportBreak element is defined such that it can be tested to see if a condition has been met which defines a break in the report. The definition of this interface dictates that a concrete instance can only be responsible for a single condition.
• XMLOutputReportVisitor: This should be capable of outputting the full xml definition of the report structure. At the moment it caters for the names of the elements, and their identifiers if present.

Home | Contact Us | Privacy Policy | Terms of Service