|
Deprecated Classes |
org.pentaho.reporting.engine.classic.core.function.AbstractCompareExpression
This can be better handled in a formula. |
org.pentaho.reporting.engine.classic.core.Anchor
Ancors should not be created this way. Add a Anchor-Style-Expression instead. This class will be removed
in 0.8.11. |
org.pentaho.reporting.engine.classic.core.AnchorElement
to create anchors, use the style-key 'Anchor-Target' instead. This class will be removed in 0.8.11. |
org.pentaho.reporting.engine.classic.core.filter.templates.AnchorFieldTemplate
the Anchor-Field has been deprecated. Use the style-key "anchor" instead. |
org.pentaho.reporting.engine.classic.core.filter.AnchorFilter
The anchor filter is deprecated now. Use the stylekey "anchor" instead. |
org.pentaho.reporting.engine.classic.core.function.bool.AndExpression
use formulas instead |
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.AnnualDateRule
|
org.pentaho.reporting.engine.classic.core.function.AverageExpression
this has been replaced by the ColumnAverageExpression. |
org.pentaho.reporting.engine.classic.core.states.CachingDataFactory
Do not use anymore. |
org.pentaho.reporting.engine.classic.core.function.strings.CapitalizeStringExpression
Use a formula instead. |
org.pentaho.reporting.engine.classic.core.modules.parser.ext.factory.base.ClassComparator
Moved to org.jfree.util |
org.pentaho.reporting.engine.classic.core.function.ColumnAverageExpression
the same can be achived with a formula "AVG([column1], [column2], [column3])" |
org.pentaho.reporting.engine.classic.core.function.ColumnDifferenceExpression
This can be done easier with a formula. |
org.pentaho.reporting.engine.classic.core.function.ColumnDivisionExpression
Use a formula |
org.pentaho.reporting.engine.classic.core.function.ColumnMaximumExpression
Use a formula |
org.pentaho.reporting.engine.classic.core.function.ColumnMinimumExpression
Use a formula |
org.pentaho.reporting.engine.classic.core.function.ColumnMultiplyExpression
Use a formula |
org.pentaho.reporting.engine.classic.core.function.ColumnSumExpression
Use a formula |
org.pentaho.reporting.engine.classic.core.function.date.CompareDateExpression
This can be solved easier using the Inline-Expression language. |
org.pentaho.reporting.engine.classic.core.function.CompareFieldsExpression
Use a formula instead. |
org.pentaho.reporting.engine.classic.core.function.numeric.CompareNumberExpression
like all compare functions, using the formula support is easier. |
org.pentaho.reporting.engine.classic.core.function.strings.CompareStringExpression
This can be done a lot easier using a simple formula. |
org.pentaho.reporting.engine.classic.core.function.ConditionalItemSumFunction
Filter the values by using a plain formula. |
org.pentaho.reporting.engine.classic.core.function.CreateGroupAnchorsFunction
It is easier to create anchors using a Style-expression. The Anchor-Field has been deprecated now. |
org.pentaho.reporting.engine.classic.core.function.CreateHyperLinksFunction
add style expressions to the 'href-target' and 'href-window' instead. It is much easier and less
confusing. |
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.DateChooserPanel
|
org.pentaho.reporting.engine.classic.core.function.DateCutExpression
The VariableDateExpression is much better suited for this purpose. |
org.pentaho.reporting.engine.classic.core.function.date.DateSpanExpression
This can be solved using a plain formula. |
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.DateUtilities
|
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.DayAndMonthRule
|
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.DayOfWeekInMonthRule
|
org.pentaho.reporting.engine.classic.core.wizard.DefaultDataSchemaModel
Use the DesignTimeDataSchemaModel instead. |
org.pentaho.reporting.engine.classic.core.layout.DefaultLayoutSupport
Like the layout support itself, this class is deprecated. There is no safe way how functions could
compute valid text-sizes before the layouting starts. |
org.pentaho.reporting.engine.classic.core.DrawableElement
This class is no longer used and will be removed in the next version. |
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.EasterSundayRule
|
org.pentaho.reporting.engine.classic.core.function.ElementColorFunction
add a style expression for the 'paint' style instead |
org.pentaho.reporting.engine.classic.core.function.ElementTrafficLightFunction
This function can be safely replaced by a formula. |
org.pentaho.reporting.engine.classic.core.function.ElementVisibilityFunction
add a style-expression for the visible style-key instead. |
org.pentaho.reporting.engine.classic.core.function.ElementVisibilitySwitchFunction
Use the RowBandingFunction to modify the band's background color directly. |
org.pentaho.reporting.engine.classic.core.modules.gui.commonswing.FileChooserService
Unused; will be removed in 4.0 |
org.pentaho.reporting.engine.classic.core.style.FontDefinition
use single properties instead. |
org.pentaho.reporting.engine.classic.core.GroupList
The group-list is a legacy class and should not be used outside the legacy handling. |
org.pentaho.reporting.engine.classic.core.function.HideElementByNameFunction
Use a formula |
org.pentaho.reporting.engine.classic.core.function.HideElementIfDataAvailableExpression
Use a Style-Expression or make proper use of the No-Data-Band |
org.pentaho.reporting.engine.classic.core.function.HideNullValuesFunction
This should be done using Style-Expressions. |
org.pentaho.reporting.engine.classic.core.ImageElement
This class is no longer used and will be removed in the next version. |
org.pentaho.reporting.engine.classic.core.style.ImmutableStyleSheet
This class is not used anywhere. It will be removed in 0.8.11. |
org.pentaho.reporting.engine.classic.core.states.IndexedMetaTableModel
Do not use, class moved into "cache" package. |
org.pentaho.reporting.engine.classic.core.states.IndexedTableModel
Do not use, class moved into "cache" package. |
org.pentaho.reporting.engine.classic.core.function.bool.IsEmptyDataExpression
Use a formula instead or make proper use of the No-Data band. |
org.pentaho.reporting.engine.classic.core.function.IsEmptyExpression
Use a Formula Instead |
org.pentaho.reporting.engine.classic.core.function.numeric.IsNegativeExpression
This can be replaced by a formula. |
org.pentaho.reporting.engine.classic.core.function.IsNullExpression
Use a Formula Instead |
org.pentaho.reporting.engine.classic.core.function.numeric.IsPositiveExpression
This can be replaced by a formula. |
org.pentaho.reporting.engine.classic.core.function.ItemColumnQuotientExpression
Use PercentageExpression instead, it's name is much clearer |
org.pentaho.reporting.engine.classic.core.layout.LegacyLayoutSupport
Like the base class, this class cannot be used to create a valid precomputation of the report layout. |
org.pentaho.reporting.engine.classic.core.util.MemoryByteArrayOutputStream
moved to LibBase |
org.pentaho.reporting.engine.classic.core.function.NegativeNumberPaintChangeFunction
The same thing can be achieved using a simple StyleExpression on the element's PAINT stylekey. |
org.pentaho.reporting.engine.classic.core.function.bool.OrExpression
use Formulas instead |
org.pentaho.reporting.engine.classic.core.function.PaintComponentFunction
Use the new Component-Element instead. It uses drawables for this job, and therefore the result looks
much better. This method does no longer work, as it depended on implementation details that are no longer
in use. |
org.pentaho.reporting.engine.classic.core.function.PaintDynamicComponentFunction
Use the new Component-Element instead. It uses drawables for this job, and therefore the result looks
much better. |
org.pentaho.reporting.engine.classic.core.parameters.ParameterUtils
|
org.pentaho.reporting.engine.classic.core.function.PercentageExpression
The same can be achieved using a simple ValueExpression. |
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.RelativeDayOfWeekRule
|
org.pentaho.reporting.engine.classic.core.modules.parser.base.ReportGenerator
Use LibLoader directly. |
org.pentaho.reporting.engine.classic.core.util.ReportProperties
This is no longer valid. The properties are a weird concept and are inherently unclean. They have been
replaced by the report environment and the bundle metadata. |
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.SerialDate
|
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.SerialDateUtilities
|
org.pentaho.reporting.engine.classic.core.ShapeElement
This class is no longer used and will be removed in the next version. |
org.pentaho.reporting.engine.classic.core.modules.output.table.base.SheetLayoutCollection
no longer used. Will be removed in the next release. |
org.pentaho.reporting.engine.classic.core.function.ShowElementByNameFunction
This can be done easier using style-expressions |
org.pentaho.reporting.engine.classic.core.function.ShowElementIfDataAvailableExpression
Use a formula instead. |
org.pentaho.reporting.engine.classic.core.modules.gui.base.date.SpreadsheetDate
|
org.pentaho.reporting.engine.classic.core.layout.StackedLayoutManager
This layout manager is no longer used. |
org.pentaho.reporting.engine.classic.core.states.datarow.StaticDataRow
Moved into main package, as this class is of general usefulness. |
org.pentaho.reporting.engine.classic.core.layout.StaticLayoutManager
This layout manager is no longer used. |
org.pentaho.reporting.engine.classic.core.style.StyleSheetCollection
This will go away. Do not use it, do not reference it, just stay out of here. |
org.pentaho.reporting.engine.classic.core.function.strings.SubStringExpression
Use a formula |
org.pentaho.reporting.engine.classic.core.modules.parser.extwriter.TemplatesWriter
No longer used. |
org.pentaho.reporting.engine.classic.core.TextElement
This class is no longer used and will be removed in the next version. |
org.pentaho.reporting.engine.classic.core.function.TextFormatExpression
Use the MessageFormatExpression instead. |
org.pentaho.reporting.engine.classic.core.function.strings.TokenizeStringExpression
Use a formula: "prefix & SUBSTITUTE(field, delimeter, replacement) & suffix" |
org.pentaho.reporting.engine.classic.core.function.strings.ToLowerCaseStringExpression
This can be solved with a formula |
org.pentaho.reporting.engine.classic.core.function.strings.ToUpperCaseStringExpression
This can be solved with a formula |
org.pentaho.reporting.engine.classic.core.function.strings.URLEncodeExpression
This can be replaced by a formula. |
org.pentaho.reporting.engine.classic.core.modules.output.xml.XMLModule
The whole basic XML output is deprecated as it cannot handle inline subreports. |
org.pentaho.reporting.engine.classic.core.modules.output.xml.XMLProcessor
The whole basic XML output is deprecated as it cannot handle inline subreports. |
org.pentaho.reporting.engine.classic.core.modules.output.xml.XMLWriter
The whole basic XML output is deprecated as it cannot handle inline subreports. |
|
Deprecated Methods |
org.pentaho.reporting.engine.classic.core.wizard.DataSchemaCompiler.compile(TableModel, Expression[], ParameterDataRow, ReportEnvironment)
pleaes pass the parameter-definition around. |
org.pentaho.reporting.engine.classic.core.elementfactory.DateFieldElementFactory.createDateElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, DateFormat, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.DateFieldElementFactory.createDateElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.DateFieldElementFactory.createDateElement(String, Rectangle2D, Color, ElementAlignment, FontDefinition, String, DateFormat, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.DateFieldElementFactory.createDateElement(String, Rectangle2D, Color, ElementAlignment, FontDefinition, String, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.LabelElementFactory.createLabelElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.LabelElementFactory.createLabelElement(String, Rectangle2D, Color, ElementAlignment, FontDefinition, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.MessageFieldElementFactory.createMessageElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.MessageFieldElementFactory.createMessageElement(String, Rectangle2D, Color, ElementAlignment, FontDefinition, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.NumberFieldElementFactory.createNumberElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, NumberFormat, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.NumberFieldElementFactory.createNumberElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.NumberFieldElementFactory.createNumberElement(String, Rectangle2D, Color, ElementAlignment, FontDefinition, String, NumberFormat, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.NumberFieldElementFactory.createNumberElement(String, Rectangle2D, Color, ElementAlignment, FontDefinition, String, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.ResourceFieldElementFactory.createResourceElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.ResourceLabelElementFactory.createResourceLabel(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.ResourceMessageElementFactory.createResourceMessage(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.TextFieldElementFactory.createStringElement(String, Rectangle2D, Color, ElementAlignment, ElementAlignment, FontDefinition, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.elementfactory.TextFieldElementFactory.createStringElement(String, Rectangle2D, Color, ElementAlignment, FontDefinition, String, String)
Use a more fine-grained approach to define this element by using the element-factory directly. |
org.pentaho.reporting.engine.classic.core.modules.output.table.html.util.HtmlEncoderUtil.encodeCSS(String, Writer)
|
org.pentaho.reporting.engine.classic.core.ReportEnvironment.encodeURL(String)
nice idea, but not used and dangerous in many cases. |
org.pentaho.reporting.engine.classic.core.parameters.FormulaParameterEvaluator.evaluate(ValidationResult, ReportParameterDefinition, ParameterContext)
This method is unsafe. Do not use it or you may open up your application to all kinds
of security risks. The method will be removed in the next release. |
org.pentaho.reporting.engine.classic.core.states.StateUtilities.findGroupByName(ReportDefinition, String)
will be removed in the next release |
org.pentaho.reporting.engine.classic.core.modules.gui.commonswing.SwingUtil.getCenterPoint()
Not used anymore, will be removed. |
org.pentaho.reporting.engine.classic.core.modules.misc.tablemodel.ScrollableResultSetTableModel.getColumnClassName(int)
|
org.pentaho.reporting.engine.classic.core.Element.getDataSource()
Whereever possible use ElementType implementations instead. |
org.pentaho.reporting.engine.classic.core.layout.DefaultSizeCalculator.getDefaultSizeCalculator(FontDefinition, boolean)
Do not use the FontDefinition, use the Font-constructor instead and instantiate the size-calculator
directly. |
org.pentaho.reporting.engine.classic.core.filter.DataRowDataSource.getField()
Required for legacy-parsing, do not use elsewhere. |
org.pentaho.reporting.engine.classic.core.TextElement.getFont()
Retrieve the required font properties directly from the stylesheet. |
org.pentaho.reporting.engine.classic.core.style.AbstractStyleSheet.getFontDefinitionProperty()
Do not use this method, access the font properties directly. This method will be removed in 0.8.11. |
org.pentaho.reporting.engine.classic.core.style.ElementStyleSheet.getFontDefinitionProperty()
This method will be removed in the next version. |
org.pentaho.reporting.engine.classic.core.modules.output.table.html.helper.StyleManager.getGlobalStyleSheet()
This method is slower than writing to the stream directly. Do not use it. |
org.pentaho.reporting.engine.classic.core.function.RowBandingFunction.getInitialTriggerValue()
use getInitialState instead. |
org.pentaho.reporting.engine.classic.core.function.ElementVisibilitySwitchFunction.getInitialTriggerValue()
use getInitialState instead. |
org.pentaho.reporting.engine.classic.core.modules.output.table.base.TableCutList.getKeys()
Always provide a buffer for performance reasons. |
org.pentaho.reporting.engine.classic.core.states.DataRowConnector.getLastDatasource(DataTarget)
no longer used. |
org.pentaho.reporting.engine.classic.core.elementfactory.ElementFactory.getLayoutCachable()
The layout cachable flag is no longer used. |
org.pentaho.reporting.engine.classic.core.function.ProcessingContext.getLayoutSupport()
the layouter works differently now. The layout-support returned here is a dummy implementation and does
no longer reflect the real layout computations. |
org.pentaho.reporting.engine.classic.core.AbstractReportDefinition.getProperties()
Report-Properties should not be used anymore. |
org.pentaho.reporting.engine.classic.core.ReportDefinition.getProperties()
This method will be removed. Report-Properties are only valid for master-reports, not for any of the
subreports. The concept of report-properties has been replaced by real parameter values. |
org.pentaho.reporting.engine.classic.core.states.ReportDefinitionImpl.getProperties()
Access to the properties should be done using the datarow. |
org.pentaho.reporting.engine.classic.core.AbstractReportDefinition.getProperty(String)
Do not use this method anymore. Use the master report's parameters instead. |
org.pentaho.reporting.engine.classic.core.Element.getValue(ExpressionRuntime)
this method should not be used directly. Use getElementType().getValue(..) instead. |
org.pentaho.reporting.engine.classic.core.parameters.ParameterUtils.initializeDefaultValues(MasterReport, ParameterContext)
|
org.pentaho.reporting.engine.classic.core.function.AbstractExpression.isActive()
The Active-Flag is no longer evaluated. We always assume it to be true. |
org.pentaho.reporting.engine.classic.core.function.Expression.isActive()
The Active-Flag is no longer evaluated. We always assume it to be true. |
org.pentaho.reporting.engine.classic.core.style.ElementStyleSheet.isAllowCaching()
has no effect. Always return true. |
org.pentaho.reporting.engine.classic.core.ReportEnvironmentDataRow.isRolesArray(String)
use "isArray" instead. |
org.pentaho.reporting.engine.classic.core.DataFactory.open()
Write your datafactories so that connections are opened on their first use. This method will
go away in the next major release. |
org.pentaho.reporting.engine.classic.core.modules.output.table.html.util.HtmlEncoderUtil.printText(PrintWriter, String, boolean)
This method is not used anywhere and therefore it will be removed. |
org.pentaho.reporting.engine.classic.core.function.AbstractExpression.setActive(boolean)
All expressions are always active. This method has no effect anymore. |
org.pentaho.reporting.engine.classic.core.style.ElementStyleSheet.setAllowCaching(boolean)
has no effect - there is always some caching now |
org.pentaho.reporting.engine.classic.core.Element.setDataSource(DataSource)
The data-source should not be used anymore. Use ElementType implementations instead. |
org.pentaho.reporting.engine.classic.core.filter.DataRowDataSource.setField(String)
Required for legacy-parsing, do not use elsewhere. |
org.pentaho.reporting.engine.classic.core.TextElement.setFont(FontDefinition)
Set the required font properties directly on the stylesheet. |
org.pentaho.reporting.engine.classic.core.style.ElementStyleSheet.setFontDefinitionProperty(FontDefinition)
This method will be removed in the next version. |
org.pentaho.reporting.engine.classic.core.function.PageFunction.setIgnorePageCancelEvents(boolean)
No longer used. |
org.pentaho.reporting.engine.classic.core.elementfactory.ElementFactory.setLayoutCachable(Boolean)
The layout cachable flag is no longer used. |
org.pentaho.reporting.engine.classic.core.AbstractReportDefinition.setProperty(String, Object)
Properties should not be used. Use the master-report's parameters instead. |
org.pentaho.reporting.engine.classic.core.MasterReport.setProperty(String, Object)
Properties should not be used. Use the master-report's parameters instead. |
org.pentaho.reporting.engine.classic.core.modules.misc.datafactory.sql.SQLReportDataFactory.setQuery(String, String)
use the full version instead. Use "removeQuery" to remove an existing query instead of setting the
query string to null. |
org.pentaho.reporting.engine.classic.core.modules.gui.commonswing.ExceptionDialog.showExceptionDialog(String, String, Exception)
use the dialog-method that accepts a parent. |