Hi Igor
Sorry for not explaining to detail. Yes by not working I mean that the
image will not refresh upon ajax refresh, the image are already on the
page it's contained within a panel. And this panel can be updated via
ajax via an selection in a dropdown. But since the image url does not
change on ajax refreshs the image are not updated. As I wrote if you
refresh the page image are reloaded by browser(firefox in this case).
I'havent fiddled with versioning...
regards Nino
Igor Vaynberg wrote:
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 nonversioned pages? no! sometimes you want this behavior,
that is why we provide NonCachingImage for the times when you dont.
-igor
On 9/10/07, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]>
wrote:
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 Martinez Vazquez Wael
<[EMAIL PROTECTED]> wrote:
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 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 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 tell if the component did not work with ajax, somehow.
regards Nino
Matej Knopp wrote:
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 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 long do you think such page renders? It shouldn't take long
than
say 5 ms on a decent machine.
-Matej
On 9/7/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
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 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 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 onComponentTag(ComponentTag tag) {
super.onComponentTag(tag);
tag.put("src", tag.getString("src") + "&rand=" +
Math.random());
}
or event better since random could give duplicate results:
protected void onComponentTag(ComponentTag tag) {
super.onComponentTag(tag);
tag.put("src", tag.getString("src") + "&autoIndex=" +
getPage().getAutoIndex());
}
Although im not sure if its safe to use autoIndex?I've put up
a
feature
request for it to be implemented.
https://issues.apache.org/jira/browse/WICKET-939
-Nino
Nino Saturnino Martinez Vazquez Wael wrote:
this is whats generated:
http://localhost:8080/thirdparty-webapp/thirdParty/?wicket:interface=:4:form:phoneA:phoneThumb:image::IResourceListener
::
regards Nino
Martijn Dashorst wrote:
The most failsafe solution to the update image using Ajax
request to
my mind is to add a random number to the url for the image
(I
thought
we already did that?).
Martijn
On 9/7/07, Nino Saturnino Martinez Vazquez Wael
<[EMAIL PROTECTED]> 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..
regards Nino
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now:
http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
