yes. but the biggest part is detaching - if you have a chart that has 10000 data points, you dont want those sitting in session/being replicated across cluster. so a detachable model will retrieve them when they are needed, but dump them before it is serialized into session. and this has an advantage of data being refreshed every request so it is up to date.

-Igor


On 6/21/06, Stefan Arentz <[EMAIL PROTECTED]> wrote:


On 6/21/06, Igor Vaynberg < [EMAIL PROTECTED]> wrote:
mm...sexy...

here is something you might want to try:

class JFreeChartImage extends Image {
    protected Resource getImageResource() {
        Chart chart=(Chart)getModelObject();
        return new JFreeChartImageResource(chart, ....
    }
}

this way your chart data will be updated from request to request and it can be detachable, etc. models rock!

Ok so by moving the Chart's data out of the Resource and into a Model I can now share that data between different components (for example having two images on the same page containing the same chart). Right?

And also moving the Chart's data (model) into a Wicket Model it allows for serialization and thus clustering?

Did I get that right?

 S.




_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user



_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to