here it is..:
https://issues.apache.org/jira/browse/WICKET-980
Eelco Hillenius wrote:
On 9/13/07, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
That would be fine, I just feel that somehow wicket coders should
somehow get at notice that the normal Image will not be updated
That would be fine, I just feel that somehow wicket coders should
somehow get at notice that the normal Image will not be updated because
the browser caches it... It could just be a comment in the jdoc..
regards Nino
Ernesto Reinaldo Barreiro wrote:
Why not use NonCachingImage?
regards
On 9/13/07, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
That would be fine, I just feel that somehow wicket coders should
somehow get at notice that the normal Image will not be updated because
the browser caches it... It could just be a comment in the jdoc..
Could you
No, it did not work for me using ajax. Until I added one of the
solutions described.
Should I provide a quickstart?
regards Nino
Igor Vaynberg wrote:
as far as i know Image works just fine with ajax. if you want an image that
is not cached use NonCachingImage.
-igor
On 9/9/07, Nino
I know(and agree), but I just feel that we should somehow warn people
that image won't work with ajax?
regards Nino
Matej Knopp wrote:
Again, try using NonCachingImage instead of Image. I does exacly what
the suggested fix does. I just overlooked it.
-Matej
On 9/10/07, Nino Saturnino
you mean when you add Image using ajax it doesnt show up?
being able to refresh something and it not working are two very different
things. if you have a nonversioned page and Image in it you will have the
exact same behavior because the url will remain stable - does that mean
Image is broken in
This has been rejected as invalid for fixing... But should'nt at least
something have been added to the component. Currently Image are not
valid for ajax calls, and you wont see the problem until you catch it in
your browser.. Either we write something in the javadocs or??? Could be
nice to
as far as i know Image works just fine with ajax. if you want an image that
is not cached use NonCachingImage.
-igor
On 9/9/07, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED]
wrote:
This has been rejected as invalid for fixing... But should'nt at least
something have been added to
so no, talking to Matej on ##wicket, the fix was this:
Resolutions are these two :
protected void onComponentTag(ComponentTag tag) {
super.onComponentTag(tag);
tag.put(src, tag.getString(src) + rand= +
Math.random());
}
or event better since random could
2 tags generating the same milisecond for the same client/session?
that looks very very very odd to me.
johan
On 9/7/07, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED]
wrote:
Actually we discussed that.
I suggested it but as Matej wrote:
don't think so. you can have two tags
This was how it was supposed to have written like:
Actually we discussed that.
I suggested it but as Matej wrote:
don't think so. you can have two tags generated in same millisecond.
As for nano might be better, lesser chance for tags being generated in
the same nanosec.
But whats wrong
Actually we discussed that.
I suggested it but as Matej wrote:
don't think so. you can have two tags generated in same millisecond.. As
for nano might be better, lesser chance for tags being generated in the
same nanosec. But whats wrong with autoindex?
Martijn Dashorst wrote:
Why not use
Why not use System.currentTimeMillis()? Or if you are really concerned
use nanotime.
Martijn
On 9/7/07, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote:
so no, talking to Matej on ##wicket, the fix was this:
Resolutions are these two :
protected void
Why not use NonCachingImage?
regards Ernesto
Nino Saturnino Martinez Vazquez Wael wrote:
Hi
How do I add keywords no-cache and etc, for a panel? Reason are that
the panel carries a image and that gets cached so when my ajax call
comes in and updates the model then the old image are shown..
Hi
How do I add keywords no-cache and etc, for a panel? Reason are that the
panel carries a image and that gets cached so when my ajax call comes in
and updates the model then the old image are shown..
regards Nino
-
To
Yes, but all those images will have a different url, or are they the
same? The milliseconds parameter is only used to distinguish between
requests, not within one.
Martijn
On 9/7/07, Matej Knopp [EMAIL PROTECTED] wrote:
Really? What's so odd about it? Say you have a page with 100 images.
How
Well, i guess with component path encoded in url, the milliseconds could do ;)
-Matej
On 9/7/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Yes, but all those images will have a different url, or are they the
same? The milliseconds parameter is only used to distinguish between
requests, not
17 matches
Mail list logo
