org.kuali.kra.common.printing

Class ReportBean

java.lang.Object

org.kuali.kra.common.printing.ReportBean

All Implemented Interfaces:

Serializable, org.kuali.rice.core.api.mo.ModelObjectBasic, org.kuali.rice.krad.bo.BusinessObject

Direct Known Subclasses:

CurrentReportBean, PendingReportBean

public abstract class ReportBean
extends Object
implements org.kuali.rice.krad.bo.BusinessObject

Rice foolishly requires beans used in DisplayTag to be BusinessObjects, so this class implements an interface whose behavior is completely inapplicable

See Also:

Serialized Form

Constructor Summary

Constructors

Constructor and Description
ReportBean()

Method Summary

Methods

Modifier and Type	Method and Description
protected org.kuali.rice.kns.web.ui.Column	createColumn(String label, String propertyName, Object property, Class clazz)
protected abstract List<org.kuali.rice.kns.web.ui.Column>	createColumns()
org.kuali.rice.kns.web.ui.ResultRow	createResultRow() Here's the story of this method: Rice found a great utility called DisplayTag (http://displaytag.sourceforge.net).
void	prepareForWorkflow()
void	refresh()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface org.kuali.rice.core.api.mo.ModelObjectBasic

toString

Constructor Detail

ReportBean

public ReportBean()

Method Detail

createColumns

protected abstract List<org.kuali.rice.kns.web.ui.Column> createColumns()

refresh

public void refresh()

Specified by:

refresh in interface org.kuali.rice.krad.bo.BusinessObject

prepareForWorkflow

public void prepareForWorkflow()

createColumn

protected org.kuali.rice.kns.web.ui.Column createColumn(String label,
                                            String propertyName,
                                            Object property,
                                            Class clazz)

createResultRow

public org.kuali.rice.kns.web.ui.ResultRow createResultRow()

Here's the story of this method: Rice found a great utility called DisplayTag (http://displaytag.sourceforge.net). I've worked with DisplayTag. It's a simple and effective tool for creating tables with a lot of inherent functionality. Rice then ruined its simplicity by creating couplings to Rice classes in the exporters (CSV, XML, and XLS) so that the basic DisplayTag behavior of exporting a table of POJOs no longer works. (These dependencies are manifested in properties set in displaytag.properties, specifically, the export..class properties. Instead of working with a collection of POJOs Rice forced the collection to be a collection of ResultRows which have a bunch of Rice framework specific properties. Each ResultRow forces the properties of the bean to be expressed as another Rice-specific type called a Column. A Column also has a bunch of Rice-framework specific properties. This is the modus operandi of Rice. Find something which has great utility and modify it until it only works to solve one kind of Rice-specific problem. In this case, they were trying to create a generic lookup solution. Along the way, they ruined a perfectly good utility API, DisplayTag. To work around this foolishness, this POJO has a factory method to create a ResultRow from itself. That ResultRow creates Column objects for each property.