In Wicket Extensions we have an ajax upload field iirc. That should
not block the pagemap...
Martijn
On Mon, Aug 2, 2010 at 4:35 PM, Johan Compagner wrote:
> maybe do the actual upload through and iframe or something that has
> its own pagemap?
>
> Or block the ui in the browser as long as the u
Thanks! I guess it's now a matter of telling the user "if you want to do
stupid stuff like this, it's going to cost you X for us to code around it."
I'm sure that should get them to stop what they're doing. :)
On Mon, Aug 2, 2010 at 10:35 AM, Johan Compagner wrote:
> maybe do the actual upload
maybe do the actual upload through and iframe or something that has
its own pagemap?
Or block the ui in the browser as long as the upload is in progress
(but then user can still do F5, but they should know that they should
wait for it)
You can also for example use a flash uploader to a servlet th
So, is there anything I can do to "fix" the problem (aside from hitting the
user on the head and telling them not to do that again)? They keep getting
the "application error" screen when they do that.
On Mon, Aug 2, 2010 at 10:27 AM, Johan Compagner wrote:
> yes that is most likely the case.
>
>
yes that is most likely the case.
On Mon, Aug 2, 2010 at 16:17, James Carman wrote:
> I have a theory about what is causing this issue. Just wanted to run it by
> you guys. In my log files, I first see this:
>
> org.apache.wicket.protocol.http.request.InvalidUrlException:
> org.apache.wicket.
I have a theory about what is causing this issue. Just wanted to run it by
you guys. In my log files, I first see this:
org.apache.wicket.protocol.http.request.InvalidUrlException:
org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null is
still locked by: Thread[http-10080-Pro
