oh ok, now I get it.
Too bad the "component" approach doesn't work. Creating a component makes
more sense to me, I wonder if it can be fixed by the framework..
thx for clearing this up!
Ronald
Harald Geritzer-2 wrote:
>
>> So what do you mean by letting the page to render the image? Do you mean
>> that every page will have the two functions above?? And what the poster
>> component needs to do then??
>
> instead of having a component providing the image you could have a page:
>
>
> public class Preview {
>
> public StreamResponse onActivate(Object[] context) {
> ...
>
> return myImageStreamResponse;
> }
> }
>
> and instead of rendering an actionlink you could use a pagelink:
>
> public Link getUserPosterImageLink() {
> return resources.createPageLink("Preview", false,
> new Object[] {userPosterImageFilename});
> }
>
>
> so the url for the image will always be
> /myapp/preview/userPosterImageFilename.
>
> hope this helps,
> harald
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/T5%3A-cache-image-created-by-StreamResponse--tp18537525p18539138.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
