Hi Maxim,
I don't see any relation between those.
If it is easy to reproduce please create a quickstart.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Nov 3, 2016 at 4:16 AM, Maxim Solodovnik
wrote:
> Hello,
>
> Recently we found
AjaxDownload changes the window location - the browser probably prepares
unloading of the page, before opening the attached download in a separate
window.
Sven
Am 03.11.2016 um 08:33 schrieb Martin Grigorov:
Hi Maxim,
I don't see any relation between those.
If it is easy to reproduce
AjaxDownload was for wicket 1.5.x (or maybe 6.x)
maybe it can be enhanced to work without unload?
On Thu, Nov 3, 2016 at 2:46 PM, Sven Meier wrote:
> AjaxDownload changes the window location - the browser probably prepares
> unloading of the page, before opening the attached
I'll try to create quick-start ASAP
On Thu, Nov 3, 2016 at 2:51 PM, Maxim Solodovnik
wrote:
> AjaxDownload was for wicket 1.5.x (or maybe 6.x)
> maybe it can be enhanced to work without unload?
>
> On Thu, Nov 3, 2016 at 2:46 PM, Sven Meier wrote:
>
>>
maybe open a second browser tab and do the download there...
On Thu, Nov 3, 2016 at 8:51 AM, Maxim Solodovnik
wrote:
> I'll try to create quick-start ASAP
>
> On Thu, Nov 3, 2016 at 2:51 PM, Maxim Solodovnik
> wrote:
>
> > AjaxDownload was for wicket
I'm afraid It would be not really Ajax .
On Thu, Nov 3, 2016 at 3:03 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> maybe open a second browser tab and do the download there...
>
> On Thu, Nov 3, 2016 at 8:51 AM, Maxim Solodovnik
> wrote:
>
> > I'll try
On Thu, Nov 3, 2016 at 8:46 AM, Sven Meier wrote:
> AjaxDownload changes the window location - the browser probably prepares
> unloading of the page, before opening the attached download in a separate
> window.
>
This could be the reason but it is the other way around of what
>> Maxim said: websocket.close() triggers the ajax download.
Nope, sorry for my English
I said
For some reason at the moment download is initiated
WebSocketBehavior::onClose is being called
so user clicks "Download", and then, as the result WebSocket#onClose() is
being called
I would
I do not know if this is possible but
1- Open a new tab
2- Set location to download URL
3- Close the new tab
That way (maybe) page does not close WebSocket connection. It would still
be "AJAX"...
On Thu, Nov 3, 2016 at 9:04 AM, Maxim Solodovnik
wrote:
> I'm afraid It
or maybe use a hidden iframe to trigger download...
On Thu, Nov 3, 2016 at 9:28 AM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> I do not know if this is possible but
>
> 1- Open a new tab
> 2- Set location to download URL
> 3- Close the new tab
>
> That way (maybe) page does not
On Thu, Nov 3, 2016 at 9:36 AM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> or maybe use a hidden iframe to trigger download...
>
this should be simpler
with the tabs some blocker may prevent it
>
> On Thu, Nov 3, 2016 at 9:28 AM, Ernesto Reinaldo Barreiro <
> reier...@gmail.com>
It seems iframe is the only option :(((
here is the JS plugin wrapping this idea:
http://johnculviner.com/jquery-file-download-plugin-for-ajax-like-feature-rich-file-downloads/
going to perform additional search
Thanks for the idea!
On Thu, Nov 3, 2016 at 3:36 PM, Ernesto Reinaldo Barreiro <
On Thu, Nov 3, 2016 at 9:40 AM, Maxim Solodovnik
wrote:
> It seems iframe is the only option :(((
>
Why so sad ?
iframe is a good option
> here is the JS plugin wrapping this idea:
> http://johnculviner.com/jquery-file-download-plugin-
>
I was hoping to get answer like: in 7.x you should use .xxx :)))
Going to create example on github and will send it for review :)
On Thu, Nov 3, 2016 at 3:43 PM, Martin Grigorov
wrote:
> On Thu, Nov 3, 2016 at 9:40 AM, Maxim Solodovnik
> wrote:
>
On Thu, Nov 3, 2016 at 9:46 AM, Maxim Solodovnik
wrote:
> I was hoping to get answer like: in 7.x you should use .xxx :)))
> Going to create example on github and will send it for review :)
>
Good! Thanks!
I think we should add AjaxDownload class either to Wicket core
+1 for wicket-stuff
On Thu, Nov 3, 2016 at 9:50 AM, Martin Grigorov
wrote:
> On Thu, Nov 3, 2016 at 9:46 AM, Maxim Solodovnik
> wrote:
>
> > I was hoping to get answer like: in 7.x you should use .xxx :)))
> > Going to create example on github
Hi,
It is a bug in Wicket Native WebSocket.
https://github.com/apache/wicket/blob/d9d142b0738e289e639165523c4190727e281519/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L310
returns a null and still we try to
Thanks for looking Martin
On 3 November 2016 at 09:07, Martin Grigorov wrote:
> Hi,
>
> It is a bug in Wicket Native WebSocket.
> https://github.com/apache/wicket/blob/d9d142b0738e289e639165523c4190
> 727e281519/wicket-native-websocket/wicket-native-
>
Hello,
I have a form which has some fields with validation attached to them.
When the user authenticates I hide some form elements.
When the form is submitted I receive a Warn log entry:
o.a.wicket.markup.html.form.Form - IFormValidator in form `form` depends on
a component that has been
Hi,
your *IForm*Validator complains about some of its dependent components
being invisible. So no need to remove any validators.
Your IFormValidator's getDependentFormComponents() should only return
visible components.
Have fun
Sven
Am 03.11.2016 um 21:40 schrieb Marcel Barbosa Pinto:
Got it. Thank you!
Em 3 de nov de 2016 20:35, "Sven Meier" escreveu:
> Hi,
>
> your *IForm*Validator complains about some of its dependent components
> being invisible. So no need to remove any validators.
>
> Your IFormValidator's getDependentFormComponents() should only
21 matches
Mail list logo