> Youre bussiness object should be in a detachable model anyway.
> If the current implementation fails. Then also clustering fails. I don't see another way. This was a great
> serializeable test we fixed a few things.
>
I think you are wrong on this. There should be no requirement that my business object should be detachable. This forces me down a design direction that I may not wish to follow. There are some really genuine cases where I may want to create a business object that implements Serializable and that I wish to keep in the session. The hangman example does exactly this. It is also a common approach for non-mission critical things like shopping baskets, questionnaires, tax calculators and so on. Some applications (especially read-mostly) just don't need persistent storage in the background because the storing of business data in the session is significantly less that the overhead of keep writing it to/from a database for each request. In these cases detaching the model to a database is just not necessary. Thus I would want to use an ordinary model that contains a serializable business object. Any form of copy/clone would prevent this highly useful design pattern.
> So it is not the other way around clustering will fail because of this.
> And again i have stressed this in other post.
> If wicket doesn't support this, i as developer must do this all by hand, I already do this currently by a
> project. There i use a copy constructor and make
> a complete new page/components/models based on the current page/components/models. This is very hard work.
>
> People can turn it off (it is/can by default i don't care) Or people can make there own factory so that for some
> pages they are going the default way
> others they do it by there own code (copy constructor) and even others they don't do nothing...
>
That is my point. I think the use of any form of cloning or copy constructor, whether done manually by yourself or built into the framework is a poor design pattern. We should try to find another way to solve it imho.
> So difficutlties in clustering i really don't see. Because the end result is the same when i do it by hand or
> not.. exactly the same.
> johan
Regards,
Chris
