-
-
2. Re: ReRender problem with mediaOutput
oichris Mar 17, 2009 6:05 AM (in response to fkj)Guess you are referring to FireFox?
Try adding a timestamp as parameter :
< f:param value="#{fileUploadBean.timeStamp}" name="time"/>
in the media input tag. Return the current timestamp from the fileUploadBean. -
3. Re: ReRender problem with mediaOutput
nbelaevski Mar 17, 2009 7:06 AM (in response to fkj)Or you can bind value attribute to the bean property that will change when image is changed.
-
4. Re: ReRender problem with mediaOutput
fkj Mar 19, 2009 1:29 PM (in response to fkj)"oichris" wrote:
Guess you are referring to FireFox?
Try adding a timestamp as parameter :
< f:param value="#{fileUploadBean.timeStamp}" name="time"/>
in the media input tag. Return the current timestamp from the fileUploadBean.
Yes, Firefox 3. Your solution worked just fine, thanks.
nbelaevski, I have also tried your solution but the image was not rendered, I have tried to bind the value attribute with the byte array that contains the image data. -
5. Re: ReRender problem with mediaOutput
nbelaevski Mar 19, 2009 1:40 PM (in response to fkj)It's not correct to use value as data bytes array. Take a look into reference guide for more information.
-
6. Re: ReRender problem with mediaOutput
sushi33 Nov 26, 2010 4:27 AM (in response to oichris)Hi Guys,
I have just run into this issue with MediaOutput and have tried Chris' fix and it does indeed work.
My question is - why? Just calling a timestamp and adding it as a parameter seems a strange fix.
-
7. Re: ReRender problem with mediaOutput
facemakersc May 25, 2011 5:17 PM (in response to sushi33)My guess is firefox was caching the result, even though it wasn't supposed to. Supplying a (never before used) unique timestamp to the url guarantees the data received won't come from a cached resource.