major
nice-to-have
minor
The superclass `JFreeChartComponent` determines that it needs to redraw itself, but the same chart is redrawn because it was not invalidated and recalculated.
Therefore, the resetCaches() method is now overridden in AbstractChartComponent and supplemented with a call to resetChart(). This ensures that after receiveModelChanged(), the chart is now invalidated and then recalculated.
Original Problem
In the Prime Tile Cockpit, various charts are configured as special tiles, e.g., “Open Items by Traffic Light Status.” This tile displays an interactive pie chart, meaning you can click on the chart’s segments (e.g., “red”) to view and edit the associated business objects. If, for example, you change the traffic light status of an open item from red to green, the chart is not updated. This remains the case even if you close the tile and reopen it. The chart that was previously displayed is rendered again and again. The chart is only updated when you exit the system or switch to a different project context in the meantime. It was noticed that the chart component is redrawn after the change (setting the traffic light status) anyway, but it does not recalculate the chart.
Test
For example, open a tile in Prime with a configured chart (e.g., Open Items by Traffic Light Status), edit one of the objects it contains, and change the partitioning attribute (e.g., traffic light status). The chart should now reflect the change—that is, it should update.