OK
Will try :)
I had an idea like this, but hoping there is some other way :)
On Thu, Sep 1, 2016 at 12:54 PM, Martin Grigorov
wrote:
> I think you should listen for the "open" message on the client side and
> once it comes then send a message to ask for the initial
I think you should listen for the "open" message on the client side and
once it comes then send a message to ask for the initial update.
Something like: Wicket.Event.subscribe(Wicket.Event.WebSocket.Opened,
function() { Wicket.WebSocket.send("initialRepaint") })
Martin Grigorov
Wicket Training
It is technically possible ... but with no effect :
What should be the steps to send component tree update on websocket client
connect?
On Thu, Sep 1, 2016 at 12:35 PM, Martin Grigorov
wrote:
> Hi Maxim,
>
> If I remember correctly it is not yet possible to write to
Hi Maxim,
If I remember correctly it is not yet possible to write to the client at
that point.
But I might be wrong.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Sep 1, 2016 at 7:11 AM, Maxim Solodovnik
wrote:
> Hello,
>
> I
Hello,
I wonder why we don't have WebSocketRequestHandler in onConnect message
handler.
I would like to perform markup update on client connect, and it seems to be
impossible without copy/pasting onEvent method code
--
WBR
Maxim aka solomax
Thank you martin! Let me try this.
On Wed, Aug 31, 2016 at 2:27 PM, Martin Grigorov
wrote:
> Hi,
>
> Put a breakpoint at RequestCycle#setResponsePage(Class, PageParameters)
> and
> see who and why is calling it. This will tell you the reason.
> If this doesn't help then
Hi,
Put a breakpoint at RequestCycle#setResponsePage(Class, PageParameters) and
see who and why is calling it. This will tell you the reason.
If this doesn't help then put breakpoints in
RestartReponseAtInterceptPageException constructors.
Martin Grigorov
Wicket Training and Consulting
Great, that's exactly what I did!
Thanks!
CN
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Bug-in-TreeTable-example-with-SelectableFolderContent-tp4675396p4675404.html
Sent from the Users forum mailing list archive at Nabble.com.
Thanks!
https://issues.apache.org/jira/browse/WICKET-6235
Sven
On 31.08.2016 11:41, ChambreNoire wrote:
Hi,
I'm using Trees for the first time and I've discovered a bug with one of the
examples.
When using SelectableFolderContent, if one does the following :
1) select a tree node/leaf
I got the same issue in Wicket 1.5, so I migrated it to 6.23, but still it
is happening.
Moreover, I used "*Session.get().replaceSession()**;*" just to reproduce
the issue. it will not be in the actual application code.
and I just used "* WebSession.get().clear(); *, *Session.get().clear(); , *
Javadoc from Session # replaceSession() says : Call() upon login to protect
against session fixation.
Until Wicket version 6.21 the destroy method did not set the session id to null.
In 6.23, Session # destroy() set session#id to null, this is why Login Page is
loaded.
Hope this helps
Thank you for your quick response.
*Session:* 30 minutes.
*Html Header:*
http://www.w3.org/TR/html4/loose.dtd;>
http://wicket.apache.org;>
-
-
Hi,
What is the session-timeout ?
Can you show the html page header ? and any java code that modify it.
François
> Le 31 août 2016 à 15:49, durairaj t a écrit :
>
> I'm migrating to wicket 6.23, createPage() is working as expected in many
> modules, but not in the
I'm migrating to wicket 6.23, createPage() is working as expected in many
modules, but not in the below scenario.
There is a search modal window in the application, which is used to search
data and keep the entire Page in session to retrieve the data back from the
session (for the Back button
I'll check what's going wrong there.
Regards
Sven
Am 31. Aug. 2016, 11:44, um 11:44, ChambreNoire schrieb:
>Hi,
>
>I'm using Trees for the first time and I've discovered a bug with one
>of the
>examples.
>
>When using SelectableFolderContent, if one does the following :
>
Hi,
I'm using Trees for the first time and I've discovered a bug with one of the
examples.
When using SelectableFolderContent, if one does the following :
1) select a tree node/leaf
2) collapse the selected node/leaf parent (effectively making the previous
selection invisible)
3) select
16 matches
Mail list logo