Yes, I figured. That's why I implemented it this way:
* when the max size exception is thrown on the server the error is
registered
* that error is fetched by my custom progress requester
* when the error is detected the client side closes the iframe responsible
for the upload
this mechanism wor
I am extending the upload component and have a problem with the maximum file
size detection. The mechanism seems to be working fine except for that it
has an user unfriendliness to it: An exception is thrown, an error message
is set and the onError event called, but the message only arrives AFTER
Hi,
I am pretty new to Wicket, yet not new to development and the web (at all).
I want to hear your advise on the following functionality which I intend to
build using Wicket:
I want to make two components that work together through ajax.
1) The first is an upload component that instead of sen
