Re: Question regarding WebSocketBehavior::onConnect message

[Maxim Solodovnik]

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 update.
> Something like: Wicket.Event.subscribe(Wicket.Event.WebSocket.Opened,
> function() { Wicket.WebSocket.send("initialRepaint") })
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, Sep 1, 2016 at 7:41 AM, Maxim Solodovnik 
> wrote:
>
> > 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 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 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
> > > >
> > >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>



-- 
WBR
Maxim aka solomax

Re: Question regarding WebSocketBehavior::onConnect message

[Martin Grigorov]

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 and Consulting
https://twitter.com/mtgrigorov

On Thu, Sep 1, 2016 at 7:41 AM, Maxim Solodovnik 
wrote:

> 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 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 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
> > >
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>

Re: Question regarding WebSocketBehavior::onConnect message

[Maxim Solodovnik]

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



-- 
WBR
Maxim aka solomax

Re: Question regarding WebSocketBehavior::onConnect message

[Martin Grigorov]

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

Question regarding WebSocketBehavior::onConnect message

[Maxim Solodovnik]

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

Re: ModalWindow.PageCreator()#createPage() is loading login page unexpectedly sometimes

[durairaj t]

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 put breakpoints in
> RestartReponseAtInterceptPageException constructors.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Aug 31, 2016 at 5:06 PM, durairaj t 
> wrote:
>
> > 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();
> , *
> > *WebSession.get().**replaceSession()*" to reproduce the issue. they are
> > also loading login page as it is happening in the application.
> >
> > I don't know the exact code or component or reason for this issue.
> >
> >
> > On Wed, Aug 31, 2016 at 10:51 AM, Francois Meillet <
> > francois.meil...@gmail.com> wrote:
> >
> > > 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
> > >
> > > François
> > >
> > >
> > >
> > > > Le 31 août 2016 à 16:21, durairaj t  a
> écrit :
> > > >
> > > > Thank you for your quick response.
> > > >
> > > > *Session:* 30 minutes.
> > > >
> > > > *Html Header:*
> > > >
> > > >  > > > http://www.w3.org/TR/html4/loose.dtd;>
> > > > http://wicket.apache.org;>
> > > >
> > > > 
> > > > type="image/ico"
> > > />
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -
> > > >  -
> > > >
> > > >
> > > >
> > > > > href="theme/pageBlocking.css">
> > > > > href="Calendar/css/jscal2.css"
> > > />
> > > > > > > href="Calendar/css/border-radius.css" />
> > > > rel="stylesheet"
> > > > href="Calendar/css/steel/steel.css" />
> > > >
> > > >
> > > >
> > > > > > > src="javascripts/pageBlocking.js">
> > > > > > > src="javascripts/aim-hrs-autocomplete.js">
> > > >
> > > 
> > > >
> > > > script>
> > > >