3. "All" I need to do now is find out why my use of a NonCachingImage together with my descended LoadableDetachableModel in the form of my web page still results in huge session size (>1MB), which is forbidden in Google App Engine. -------------------------------------------------------------------------------- I have fixed my problem of a WebPage's NonCachingImage holding onto an image's data and thus causing a user's session size to get very large indeed. The model passed to the NonCachingImage was descended from LoadableDetachableModel.
Instead, I now descend my model from LoadableDetachableModel. ItemImageResource is a class I descend from DynamicImageResource by implementing its abstract method protected byte[] getImageData(). This method: · constructs a ByteArrayResource instance · using this instance to yield a IResourceStream · uses the resource stream to yield an InputStream · reads from this input stream into the byte array, which is returned by the method. This shrinks the session size to much closer to where I want it, with no image data being included in it. If anyone wants any sample code, then I shall post it here. Alternatively, if anyone shouts "No: this is not the way to do it!" then I shall be listening.... Ian Marshall -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Choice-of-Resource-for-my-Image-component-tp3342289p3414698.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
