Re: WebSocket concurrent modification

On Thu, May 28, 2020 at 9:43 AM fanfy wrote: > Hello,I finally found the problem ... It seems that I didn't understood > very > well how to use WebSocketMessageBroadcaster from wicket-spring-boot. The > proper way to broadcast websocket messages from an ajax ca

Re: WebSocket concurrent modification

Updated the sample application websocket-test.tar <http://apache-wicket.1842946.n4.nabble.com/file/t375849/websocket-test.tar> -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f184294

Re: WebSocket concurrent modification

Hello,I finally found the problem ... It seems that I didn't understood very well how to use WebSocketMessageBroadcaster from wicket-spring-boot. The proper way to broadcast websocket messages from an ajax call is to use org.apache.wicket.protocol.ws.api.WebSocketPushBroadcaster with an additional

Re: WebSocket concurrent modification

09:59, fanfy wrote: Hello, Maybe you can help me with a problem related to wicket 8.8.0 with websocket. Sometimes (usually when there are many ajax request in a short time interval) I encounter ConcurrentModificationException. The page store saving is synchronous. I created a sample project

WebSocket concurrent modification

Hello, Maybe you can help me with a problem related to wicket 8.8.0 with websocket. Sometimes (usually when there are many ajax request in a short time interval) I encounter ConcurrentModificationException. The page store saving is synchronous. I created a sample project (attached websocket

Re: WebSocket onClose/onError/onAbort is not being called

being called > > > > So my application doesn't get notified the connection has been closed > > > > > > > > > > > > > Then it must be somewhere in Wicket. > > > Check that [2] is called. > > > > > > > Yes it is called > >

Re: WebSocket onClose/onError/onAbort is not being called

hen [3], then [4]. From here on it is Wicket Event propagation [5]. It > > > > [3] and [4] are not called > As you can see from the log branch at > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websoc

Re: WebSocket onClose/onError/onAbort is not being called

> > >> Then [3], then [4]. From here on it is Wicket Event propagation [5]. It >> > > [3] and [4] are not called > As you can see from the log branch at > > https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/

Re: WebSocket onClose/onError/onAbort is not being called

en it must be somewhere in Wicket. > Check that [2] is called. > Yes it is called > Then [3], then [4]. From here on it is Wicket Event propagation [5]. It > [3] and [4] are not called As you can see from the log branch at https://github.com/apache/wicket/blob/d43c68c0126306021a1

Re: WebSocket onClose/onError/onAbort is not being called

find your behavior if it is not enabled or any of if its component hierarchy is disabled/invisible. 2. https://github.com/apache/wicket/blob/d43c68c0126306021a12afbfe7876a36612fbbc3/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketP

Re: WebSocket onClose/onError/onAbort is not being called

https://github.com/apache/wicket/blob/master/wicket-native-websocket/wicket-native-websocket-javax/src/main/java/org/apache/wicket/protocol/ws/javax/WicketEndpoint.java#L92 > > > On Fri, May 1, 2020 at 12:21 PM Maxim Solodovnik > wrote: > > > Hello, > > > > I'm h

Re: WebSocket onClose/onError/onAbort is not being called

Hi Maxim, If WicketEndpoint#onError() [1] is not called then probably there is a bug in Tomcat. I suggest you to post this question at Tomcat's users@. 1. https://github.com/apache/wicket/blob/master/wicket-native-websocket/wicket-native-websocket-javax/src/main/java/org/apache/wicket/protocol

WebSocket onClose/onError/onAbort is not being called

Hello, I'm having weird situation: WebSocket connection is closed on page reload, but none of my onClose/onError/onAbort handlers are being called I have changed wicket version to latest SNAPSHOT and got some debug logs: *ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100 [EventExec-e2-t9

Re: MetaData for websocket connections

the registry can use WebSocketConnection's > > getApplication().getName(), getSessionId() and getKey() to construct the > > key. > > > > MetaData would do the job as well, but I'd prefer to not add more > > functionality unless really needed. > > > > Regar

Re: MetaData for websocket connections

o construct the > key. > > MetaData would do the job as well, but I'd prefer to not add more > functionality unless really needed. > > Regards, > Martin > > On Wed, Mar 25, 2020 at 6:30 PM Thomas Heigl wrote: > > > Hi all, > > > > I'd like to add metadata

Re: MetaData for websocket connections

. MetaData would do the job as well, but I'd prefer to not add more functionality unless really needed. Regards, Martin On Wed, Mar 25, 2020 at 6:30 PM Thomas Heigl wrote: > Hi all, > > I'd like to add metadata to websocket connections. For instance, which > events or channels

MetaData for websocket connections

Hi all, I'd like to add metadata to websocket connections. For instance, which events or channels a connection is subscribed to. What do you think about adding MetaDataEntry[] metaData to connections and setMetaData/getMetaData to IWebSocketConnection? Best regards, Thomas

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

This was an Apache Tomcat issue. Having the same problem with 8.5.16 version it ceased when upgrading to 8.5.50. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail:

Re: WebSocket

Hello, Indeed, it works with Tomcat 9!Thanks a lot for your help. Virginie On Tue, 2019-02-19 at 19:39 +0700, Maxim Solodovnik wrote: > Or maybe with Tomcat-7 you need Wicket-7 and wicket-native-websocket-tomcat > > On Tue, 19 Feb 2019 at 18:44, Maxim Solodovnik wrote: > > S

Re: WebSocket

Or maybe with Tomcat-7 you need Wicket-7 and wicket-native-websocket-tomcat On Tue, 19 Feb 2019 at 18:44, Maxim Solodovnik wrote: > > Shot in the dark: tomcat 7 is too old ... > Does it work with tomcat 8/8.5/9 ? > > On Tue, Feb 19, 2019, 18:30 Virginie Garcin wrote: >>

WebSocket

Hello, I'm trying to use WebSocket in Wicket 8.3.0, with Tomcat 7.0.85. In pom, I have: org.apache.wicket wicket-native-websocket-javax ${wicket.version} In web.xml, I did change the WicketFilter class name

Re: WebSocket tests fail after migration to Wicket 8

Yes, I can confirm 8.2.0-SNAPSHOT works. Thank you, Manfred -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional

Re: WebSocket tests fail after migration to Wicket 8

Hi, you probably found an issue with we recently fixed : https://issues.apache.org/jira/browse/WICKET-6588 Could you test your code using 8.2.0-SNAPSHOT version? Thank you. On 29/09/2018 16:58, Manfred Bergmann wrote: Hi. I’m using a WebSocket on a component of a page based

WebSocket tests fail after migration to Wicket 8

Hi. I’m using a WebSocket on a component of a page based on WebSocketBehavior. It’s working fine when running the app. But the tests of the Panel fail, in contrast to Wicket 7 with: Caused by: java.lang.NullPointerException

Re: WebSocket and timeout

Sorry, Misread it :( I actually using both. Ajax request refreshing HTTP session and binary ping refreshing websocket connection and being ignored WBR, Maxim (from mobile, sorry for the typos) On Sep 19, 2017 02:49, "Martin Grigorov" <mgrigo...@apache.org> wrote: > Hi, >

Re: WebSocket and timeout

Hi, @Maxim: the problem Manfred faces is not that the Http Session expires but that the WebSocket connection is closed by the web container due to inactivity. @Manfred: I'd use server-side timer that uses the IWebSocketConnectionRegistry to send the heartbeat message to all connected clients

Re: WebSocket and timeout

Hello Manfred, AFAIK websocket ping messages will not update HTTP session. You can set up AbstractAjaxTimerBehavior or send pure JS HTTP request to refresh the session On Sat, Sep 16, 2017 at 7:34 PM, Manfred Bergmann <m...@software-by-mabe.com> wrote: > > Hi, > > On Sat, Sep 1

Re: WebSocket and timeout

t; This is a good start! But if there is a proxy involved then you will need to do the same there too. Better send heartbeat messages once in a while, e.g. every minute. OK. I'm not exactly certain how I would do that. Do you mean a timer on the server side which sends some message over the web

Re: WebSocket and timeout

Hi, On Sat, Sep 16, 2017 at 1:32 PM, Manfred Bergmann wrote: > Found a different solution. > > Followed the advice here: > https://issues.apache.org/jira/browse/WICKET-5453 > > Where you can set the default idle timeout on the > WebSocketServerContainerInitializer. >

Re: WebSocket and timeout

Found a different solution. Followed the advice here: https://issues.apache.org/jira/browse/WICKET-5453 Where you can set the default idle timeout on the WebSocketServerContainerInitializer. Manfred -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

Re: WebSocket and timeout

elps me, except that the not yet released > version 7.8.1 fixes something regarding WebSockets. But I don't know if it's > that. > > The thing is, that I have a one page application. Meaning the page itself > doesn't ever refresh. Only panels are reloaded here and there via Ajax. > One

Re: WebSocket and timeout

and there via Ajax. One of those panels uses a WebSocket. The WebSocket times out even if I move away from this particular panel. After the WebSocket has timed out it's only to possible to really reload the page to re-activate it. So, preferably I'd like to WebSocket to not expire before the session

Re: WebSocket and timeout

are-by-mabe.com> wrote: > Hi. > > I’m having a problem with WebSocket timeouts. > One panel (currently) of a page uses a WebSocket to push data and re-render > something. > Leaving the browser untouched the WebSocket will timeout after 5 minutes: > —- > [ERROR] 2017-09-15 16:5

WebSocket and timeout

Hi. I’m having a problem with WebSocket timeouts. One panel (currently) of a page uses a WebSocket to push data and re-render something. Leaving the browser untouched the WebSocket will timeout after 5 minutes: —- [ERROR] 2017-09-15 16:57:46.566 [Scheduler-1197176722

Re: Websocket replacing a panel which uses websockets

Done https://issues.apache.org/jira/browse/WICKET-6458 On 29 August 2017 at 18:29, Martin Grigorov wrote: > Hi, > > Please file a ticket! > It should be easy to implement it. > Thanks! > > On Aug 29, 2017 17:15, "Peter Henderson" >

Re: Websocket replacing a panel which uses websockets

Hi, Please file a ticket! It should be easy to implement it. Thanks! On Aug 29, 2017 17:15, "Peter Henderson" wrote: > Hi All, > > I've run into a possible bug. > > I've a page which initially shows a "loading..." animation panel. > This panel uses web sockets to

Websocket replacing a panel which uses websockets

Hi All, I've run into a possible bug. I've a page which initially shows a "loading..." animation panel. This panel uses web sockets to trigger background loading. (WebSocketBehavior::onConnected starts the background loading) When the background loading has completed (onEvent =>

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

Could you solve the problem ? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/After-upgrade-to-Wicket-7-6-0-WebSocket-logs-Broken-pipe-tp4676630p4678119.html Sent from the Users forum mailing list archive at Nabble.com

Re: Websocket redirect wrong url

On Wed, May 24, 2017 at 12:18 PM, Peter Henderson < peter.hender...@starjar.com> wrote: > On 24 May 2017 at 11:05, Peter Henderson > wrote: > > > > > > > On 23 May 2017 at 22:24, Martin Grigorov wrote: > > > >> Hi, > >> > >> I'm afraid a

Re: Websocket redirect wrong url

On 24 May 2017 at 11:05, Peter Henderson wrote: > > > On 23 May 2017 at 22:24, Martin Grigorov wrote: > >> Hi, >> >> I'm afraid a quickstart would be needed to be able to tell what goes wrong >> there. >> > > Thanks for looking, I thought you'd

Re: Websocket redirect wrong url

o a 404 > > > > > > Scenario. > > 1) User is on fat bookmarkable page [1] > > 2) Ajax onClick redirects to non bookmarkable SendMessagePage > > 3) SendMessage page uses websockets + background threads. > > 4) SendMessage page receives a websocket push even

Re: Websocket redirect wrong url

t; Hi all. > > > I'm seeing a strange redirect problem which leads to a 404 > > > Scenario. > 1) User is on fat bookmarkable page [1] > 2) Ajax onClick redirects to non bookmarkable SendMessagePage > 3) SendMessage page uses websockets + background threads. > 4) Sen

Websocket redirect wrong url

Hi all. I'm seeing a strange redirect problem which leads to a 404 Scenario. 1) User is on fat bookmarkable page [1] 2) Ajax onClick redirects to non bookmarkable SendMessagePage 3) SendMessage page uses websockets + background threads. 4) SendMessage page receives a websocket push event which

Re: "/websocket/closed" is not working in IE11

only begins :) > > On Mon, Apr 10, 2017 at 2:04 AM, Martin Grigorov <mgrigo...@apache.org> > wrote: > >> On Sat, Apr 8, 2017 at 11:41 AM, Maxim Solodovnik <solomax...@gmail.com> >> wrote: >> >> > Hello All, >> > >> > I

Re: "/websocket/closed" is not working in IE11

Weird enough, quickstart works :( Investigation only begins :) On Mon, Apr 10, 2017 at 2:04 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > On Sat, Apr 8, 2017 at 11:41 AM, Maxim Solodovnik <solomax...@gmail.com> > wrote: > > > Hello All, > > > >

Re: "/websocket/closed" is not working in IE11

On Sat, Apr 8, 2017 at 11:41 AM, Maxim Solodovnik <solomax...@gmail.com> wrote: > Hello All, > > I just have noticed "/websocket/closed" is not working in IE11 > handler set via > Wicket.Event.subscribe("/websocket/closed", function() {}) > Is n

"/websocket/closed" is not working in IE11

Hello All, I just have noticed "/websocket/closed" is not working in IE11 handler set via Wicket.Event.subscribe("/websocket/closed", function() {}) Is not fired The following message displayed in console instead: SCRIPT12030: WebSocket Error: Network Error 12030, The connec

How to add some data to ajax and websocket response?

Hi, I am trying to solve WICKET-5588. I want to add some ordering information (key-value) to responses for ajax and websocket. This information then will be read on client side (JS) to handle proper processing order of responses. But I cannot find a good entry point to add such generic

Re: Wicket Websocket - Exception is logged in WicketEndpoint if the user is closing the browser

://twitter.com/mtgrigorov On Sat, Jan 28, 2017 at 8:40 PM, Marc <marcgiff...@web.de> wrote: > It seems that this exception only occurs in Google Chrome... > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/Wicket-Websocket-Exception-is-logged

Re: Wicket Websocket - Exception is logged in WicketEndpoint if the user is closing the browser

It seems that this exception only occurs in Google Chrome... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-Websocket-Exception-is-logged-in-WicketEndpoint-if-the-user-is-closing-the-browser-tp4676886p4676889.html Sent from the Users forum mailing list archive

Wicket Websocket - Exception is logged in WicketEndpoint if the user is closing the browser

e host) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:315) ~[tomcat-embed-websocket-8.5.6.jar:8.5.6] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:258) ~[tomcat-embed-websocket-8.5.6.jar

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

<ilgro...@apache.org> wrote: On 04/01/2017 10:14, Martin Grigorov wrote: Hi, Have you updated Tomcat version too? I don't see any reason why changes in Wicket Native WebSocket could lead to this. In the same time there were many improvements in Tomcat WebSocket code, and this mig

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

wrote: > On 04/01/2017 10:14, Martin Grigorov wrote: > >> Hi, >> >> Have you updated Tomcat version too? >> I don't see any reason why changes in Wicket Native WebSocket could lead >> to >> this. >> In the same time there were many improveme

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

On 04/01/2017 10:29, Francesco Chicchiriccò wrote: On 04/01/2017 10:14, Martin Grigorov wrote: Hi, Have you updated Tomcat version too? I don't see any reason why changes in Wicket Native WebSocket could lead to this. In the same time there were many improvements in Tomcat WebSocket code

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

On 04/01/2017 10:14, Martin Grigorov wrote: Hi, Have you updated Tomcat version too? I don't see any reason why changes in Wicket Native WebSocket could lead to this. In the same time there were many improvements in Tomcat WebSocket code, and this might led to a regression. Hi, this happens

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

Hi, Have you updated Tomcat version too? I don't see any reason why changes in Wicket Native WebSocket could lead to this. In the same time there were many improvements in Tomcat WebSocket code, and this might led to a regression. Martin Grigorov Wicket Training and Consulting https

After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

Hi all, after upgrading to Wicket 7.6.0 [1], this code [2] is causing the following error in the logs: 10:02:16.300 ERROR org.apache.wicket.protocol.ws.javax.WicketEndpoint - An error occurred in web socket connection with id : 0 java.io.IOException: Broken pipe at

Re: WebSocket ConnectedMessage not Serializable

Ha! You've already fixed it. Ignore my pull request. (I spent too much time getting my scala -> java code compiling) Thanks Peter.

Re: WebSocket ConnectedMessage not Serializable

https://issues.apache.org/jira/browse/WICKET-6282 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Sat, Nov 19, 2016 at 4:41 PM, Martin Grigorov wrote: > Hi Peter, > > I don't see a problem to make all msgs serializable. > Please create a

Re: WebSocket ConnectedMessage not Serializable

Hi Peter, I don't see a problem to make all msgs serializable. Please create a ticket! With a Pull Request/Patch would be awesome! Thank you! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Sat, Nov 19, 2016 at 3:46 PM, Peter Henderson <

WebSocket ConnectedMessage not Serializable

Hi all. Wicket 7.3.0 Native web sockets. Tomcat 8.5.5 I am trying to do background processing with results being pushed to a client as they become available. I store the connected message when a web socket connection is made [1]. This is used to fire push data to a single client/page [2] A

Re: WebSocket close is being called if AjaxDownloader is used

gt;>>>>>> 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 :) > > >>>>>>>> >

Re: WebSocket close is being called if AjaxDownloader is used

ke: 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,

Re: WebSocket close is being called if AjaxDownloader is used

:43 PM, Martin Grigorov < >>>>>>>> mgrigo...@apache.org >>>>>>>> wrote: >>>>>>>> >>>>>>>> On Thu, Nov 3, 2016 at 9:40 AM, Maxim Solodovnik < >>>>>>>> solomax...@gmail.com>

Re: WebSocket close is being called if AjaxDownloader is used

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 < solomax...@gmail.com wrote: I'm afraid It would be not really Ajax . On Thu, Nov 3, 2016 at 3:03 PM, Ernesto Reinal

Re: WebSocket close is being called if AjaxDownloader is used

gt;>>>>> >>>>>>> solomax...@gmail.com> >>>>> >>>>>> wrote: >>>>>>>> >>>>>>>> It seems iframe is the only option :((( >>>>>>>>> >>>>>>&g

Re: WebSocket close is being called if AjaxDownloader is used

iframe is the only option :((( >>>>>>>> >>>>>>>> Why so sad ? >>>>>>> iframe is a good option >>>>>>> >>>>>>> >>>>>>> here is the JS plugin wrapping this idea: >&g

Re: WebSocket close is being called if AjaxDownloader is used

>>> iframe is a good option >>>>>>> >>>>>>> >>>>>>> here is the JS plugin wrapping this idea: >>>>>>>> http://johnculviner.com/jquery-file-download-plugin- >>>>>>>> for-ajax

Re: WebSocket close is being called if AjaxDownloader is used

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 close WebSocket connection. It would still be "AJAX"..

Re: WebSocket close is being called if AjaxDownloader is used

t; > http://johnculviner.com/jquery-file-download-plugin- > > >> > > for-ajax-like-feature-rich-file-downloads/ > > >> > > going to perform additional search > > >> > > > > >> > > Thanks for the idea! > > >>

Re: WebSocket close is being called if AjaxDownloader is used

>> > > going to perform additional search > >> > > > >> > > Thanks for the idea! > >> > > > >> > > On Thu, Nov 3, 2016 at 3:36 PM, Ernesto Reinaldo Barreiro < > >> > > reier...@gmail.com> wrote: > >>

Re: WebSocket close is being called if AjaxDownloader is used

gt; > > > >> > > > 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 >> > > > &g

Re: WebSocket close is being called if AjaxDownloader is used

aybe 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 > > > > &g

Re: WebSocket close is being called if AjaxDownloader is used

; > > > > 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 kn

Re: WebSocket close is being called if AjaxDownloader is used

gt; > > > 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

Re: WebSocket close is being called if AjaxDownloader is used

> > > > > > 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 loca

Re: WebSocket close is being called if AjaxDownloader is used

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 &g

Re: WebSocket close is being called if AjaxDownloader is used

- 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 <solomax...@gmail.com> >

Re: WebSocket close is being called if AjaxDownloader is used

> 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 close WebSocket connection. It would still >

Re: WebSocket close is being called if AjaxDownloader is used

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 <solomax...@gmail.com> > wrote: > >> I'm afraid It would be not really Ajax . >> >> On Thu, N

Re: WebSocket close is being called if AjaxDownloader is used

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 <solomax...@gmail.com> wrot

Re: WebSocket close is being called if AjaxDownloader is used

>> 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 bein

Re: WebSocket close is being called if AjaxDownloader is used

on the client side, the last triggers WebSocket#onClose() at the server side > > 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 please create a quic

Re: WebSocket close is being called if AjaxDownloader is used

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

Re: WebSocket close is being called if AjaxDownloader is used

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

Re: WebSocket close is being called if AjaxDownloader is used

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: > >>

Re: WebSocket close is being called if AjaxDownloader is used

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

Re: WebSocket close is being called if AjaxDownloader is used

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

Re: WebSocket close is being called if AjaxDownloader is used

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

WebSocket close is being called if AjaxDownloader is used

Hello, Recently we found weird behavior of AjaxDownloader (similar to this [1] one) For some reason at the moment download is initiated WebSocketBehavior::onClose is being called What is the reason for this?

Re: Websocket message from Spring bean

n Grigorov <mgrigo...@apache.org> wrote: > >> You use request and session scoped Spring beans in WebSocket request >> because such requests are not processed by Servlet filters and Spring has >> no chance to set its proxy objects as request/session attributes. >> >&g

Re: WebSocket Filter to open a Hibernate Session

Hi Martin, That's something I figured out as well, the bypassing of the Filters by WebSocket requests. I did as you said and implemented a custom IRquestCycleListener to respond on the onBeginRequest & onEndRequest in case there is a WebSocketRequest. This is working correctly now! Th

Re: WebSocket Filter to open a Hibernate Session

base using Hibernate. > > This is where it fails, giving the message: > /Caused by: org.hibernate.HibernateException: No Hibernate Session > bound to thread, and configuration does not allow creation of non- > transactional one here/ > > I know this fails due to the

WebSocket Filter to open a Hibernate Session

: No Hibernate Session bound to thread, and configuration does not allow creation of non- transactional one here/ I know this fails due to the fact that WebSocket events don't go through the normal filters, e.g. OpenSessionInViewFilter that I'm using. *My question:* Where can I create a hook where I can

Re: Cross-Site Websocket Hijacking question

://twitter.com/mtgrigorov On Wed, Mar 18, 2015 at 8:42 AM, Gergely Nagy foge...@gmail.com wrote: Hi fellow Wicketers, I have a question regarding CSWH. I was reading this article recently: http://www.notsosecure.com/blog/2014/11/27/how-cross-site-websocket-hijacking-could-lead-to-full-session-compromise

Cross-Site Websocket Hijacking question

Hi fellow Wicketers, I have a question regarding CSWH. I was reading this article recently: http://www.notsosecure.com/blog/2014/11/27/how-cross-site-websocket-hijacking-could-lead-to-full-session-compromise/ It made me wondering how can I implement my protection against this kind of attack? My

Re: JSR356 Websocket with Wicket 6.18

...@visma.com wrote: I forked Wicket to my github repo and took a look at it. Compiling wicket-native-websocket-javax with Java 6 and Wicket 6.19.0-SNAPSHOT was no problem at all, my problem popped up when I tried to get the embedded jetty server to run the test case. It fails

Re: JSR356 Websocket with Wicket 6.18

I forked Wicket to my github repo and took a look at it. Compiling wicket-native-websocket-javax with Java 6 and Wicket 6.19.0-SNAPSHOT was no problem at all, my problem popped up when I tried to get the embedded jetty server to run the test case. It fails with WebSocket connection to 'ws

Re: JSR356 Websocket with Wicket 6.18

://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 5:02 PM, Alexander Landsnes Keül alexander.landsnes.k...@visma.com wrote: I forked Wicket to my github repo and took a look at it. Compiling wicket-native-websocket-javax with Java 6 and Wicket 6.19.0-SNAPSHOT was no problem at all, my problem popped

Re: JSR356 Websocket with Wicket 6.18

url to your github repo ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 28, 2015 at 5:02 PM, Alexander Landsnes Keül alexander.landsnes.k...@visma.com wrote: I forked Wicket to my github repo and took a look at it. Compiling wicket-native-websocket

  1   2   >