actually, shouldn't it be IResource extends Serializable?
that way nested implementations would be serialiable too...
i think we need to make resources smarter about serializing... StaticImageResource for example should definitely have a transient IResource field in the end... ;-)
Johan Compagner wrote:
Our clone by serialize did encounter a few serialization exceptions for example
all the Resources (like image). Should we make AbstractResource serializeable?
those can be in the session..
johan
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
