Re: Statful image

2011-09-07 Thread vineet semwal
same as what joechen said but in a little different way if the Image resource reference is null the resource is just not added to the current available application sharedresources, it is treated in stateful way ,the url generated for such a image is not bookmarkable .. its mentioned in the javdo

Re: Statful image

2011-09-07 Thread Jochen Mader
Uh, sorry :) It all comes doen to the handling of shared and-nonshared resources. If a resource is non-shared (read: not registered with sharedresources). If the Image resource is null it can't assume that it's shared, therefore handling is at a non-shared/stateful resource. On Wed, Sep 7, 2011 at

Re: Statful image

2011-09-07 Thread Martin Grigorov
Would you share your knowledge with us ? :-) On Wed, Sep 7, 2011 at 12:33 PM, Jochen Mader wrote: > Found it shortly after my mail (as always). Never mind. > Am 07.09.2011 09:31 schrieb "Jochen Mader" : >> We just stumbled upon the following code in the Wicket(1.4.17) Image >> class getStatelessH

Re: Statful image

2011-09-07 Thread Jochen Mader
Found it shortly after my mail (as always). Never mind. Am 07.09.2011 09:31 schrieb "Jochen Mader" : > We just stumbled upon the following code in the Wicket(1.4.17) Image > class getStatelessHint method: > return (getImageResource() == null || getImageResource() == > localizedImageResource.getReso

Statful image

2011-09-07 Thread Jochen Mader
We just stumbled upon the following code in the Wicket(1.4.17) Image class getStatelessHint method: return (getImageResource() == null || getImageResource() == localizedImageResource.getResource()) && localizedImageResource.isStateless) My question is: Why does an image become stateful because of