On Fri, Feb 22, 2019 at 4:02 AM kyc wrote:
> I applied the SessionPerTabHttpSessionStore and SessionPerTabBehavior (by
> adding cookie to session storage) in our site (ref. to
> https://issues.apache.org/jira/browse/WICKET-6358
> https://github.com/martin-g/blogs/tree/master/session-per-tab
> whi
Yes. Very similar problem. Finally, we choose to display the message when
clicking the submit button instead.
Thank you very much anyway.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To uns
Although not exactly the same, it might be security related:
https://stackoverflow.com/questions/54600938/chrome-browser-version-72-0-3626-96-bug-triggering-input-type-file-click-fi
Try with a custom modal dialog instead of confirm().
Sven
Am 22.02.19 um 04:32 schrieb kyc:
I don't have probl
I don't have problem running the following code with Chrome version 69 but
the file browser cannot be displayed after the confirmation message in
Chrome 72.0.3626.109. Anyone can help?
FileUploadField fileUploadField = new FileUploadField("fileUploads");
fileUploadField.add(AttributeModifier.repl
LoginPage(Page).onBeforeRender() line: 808
Does it mean the Page.class 808 ?
Page.class line 808 : getSession().bind();
/**
*
* @see org.apache.wicket.Component#onBeforeRender()
*/
@Override
protected void onBeforeRender()
{
I applied the SessionPerTabHttpSessionStore and SessionPerTabBehavior (by
adding cookie to session storage) in our site (ref. to
https://issues.apache.org/jira/browse/WICKET-6358
https://github.com/martin-g/blogs/tree/master/session-per-tab
which causes the stateless login page creates new session
On Thu, Feb 21, 2019, 18:29 Matteo Alessandroni
wrote:
>
>
> On 21/02/19 16:43, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni <
> skylar...@apache.org>
> > wrote:
> >
> >>
> >> On 21/02/19 16:30, Martin Grigorov wrote:
> >>> On Thu, Feb 21, 2019 at 5:24 PM Matteo
On 21/02/19 16:43, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni
wrote:
On 21/02/19 16:30, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni <
skylar...@apache.org>
wrote:
On 21/02/19 16:07, Martin Grigorov wrote:
On Thu, Feb 21, 2
On Thu, Feb 21, 2019 at 5:35 PM Matteo Alessandroni
wrote:
>
>
> On 21/02/19 16:30, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni <
> skylar...@apache.org>
> > wrote:
> >
> >> On 21/02/19 16:07, Martin Grigorov wrote:
> >>> On Thu, Feb 21, 2019 at 4:41 PM Matteo A
On 21/02/19 16:30, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni
wrote:
On 21/02/19 16:07, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni <
skylar...@apache.org>
wrote:
On 21/02/19 12:14, Martin Grigorov wrote:
On Thu, Feb 21, 20
On Thu, Feb 21, 2019 at 5:24 PM Matteo Alessandroni
wrote:
> On 21/02/19 16:07, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni <
> skylar...@apache.org>
> > wrote:
> >
> >> On 21/02/19 12:14, Martin Grigorov wrote:
> >>> On Thu, Feb 21, 2019 at 12:11 PM Matteo Ales
On 21/02/19 16:07, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni
wrote:
On 21/02/19 12:14, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
matteo.alessandr...@tirasa.net> wrote:
Hi,
On 21/02/19 11:05, Martin Grigorov wrote:
When t
On Thu, Feb 21, 2019 at 4:41 PM Matteo Alessandroni
wrote:
> On 21/02/19 12:14, Martin Grigorov wrote:
> > On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
> > matteo.alessandr...@tirasa.net> wrote:
> >
> >> Hi,
> >>
> >> On 21/02/19 11:05, Martin Grigorov wrote:
> >>> When the WebSocket co
On 21/02/19 12:14, Martin Grigorov wrote:
On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
matteo.alessandr...@tirasa.net> wrote:
Hi,
On 21/02/19 11:05, Martin Grigorov wrote:
When the WebSocket connection is established (maybe when the page is
loaded) you should see an entry in the Net
On Thu, Feb 21, 2019 at 12:11 PM Matteo Alessandroni <
matteo.alessandr...@tirasa.net> wrote:
> Hi,
>
> On 21/02/19 11:05, Martin Grigorov wrote:
> > When the WebSocket connection is established (maybe when the page is
> > loaded) you should see an entry in the Network tab.
> > If you select this
Hi,
On 21/02/19 11:05, Martin Grigorov wrote:
When the WebSocket connection is established (maybe when the page is
loaded) you should see an entry in the Network tab.
If you select this entry then on the right-side you should see any WS
messages to/from the server.
Yes I know how about WS debu
The stacktrace says: LoginPage(Page).onBeforeRender() line: 808
What is the code at lines 800-808 in your LoginPage class ?
On Thu, Feb 21, 2019 at 11:56 AM kyc wrote:
> After logout page, it will redirect to the login page. I have already
> converted the login and logout pages to Stateless pag
On Thu, Feb 21, 2019 at 11:40 AM Matteo Alessandroni
wrote:
> Hi,
>
> thanks for the answer!
> There are no js errors and browser devtool does not show any WS request
> so I'm not sure it's passing the correct body.
>
When the WebSocket connection is established (maybe when the page is
loaded) y
After logout page, it will redirect to the login page. I have already
converted the login and logout pages to Stateless page by adding
@StatelessComponent with the StatelessChecker to them (without exception in
runtime). I don't know why the bind() is still being called and new session
is created
Hi,
thanks for the answer!
There are no js errors and browser devtool does not show any WS request
so I'm not sure it's passing the correct body.
Anyway, if I add:
resourceCreateEvent.getTarget().appendJavaScript(String.format("addEndpoint('%s',
'%s', '%s');",
resourceCre
Hi,
Check the browser's Dev Tools' console for any JavaScript errors.
If there are no errors then check in the DevTools Network tab whether the
WebSocket response frame contains the JS code in its body. It must be
inside XML element. If it is not there at all then it must be
something on the serv
Hi,
we have a logic where a websocket message is sent from an "onEvent()"
method [1] and catched in a WebSocketBehavior class [2].
Then, a call to a js method "addEndpoint()"[3] must be executed.
Our problem is that the js code "addEndpoint(...)" inside
"handler.appendJavaScript(...)" [4] is n
Hi,
The question is what leads to the call of Session#bind().
While the debugger is at Session#bind() see what is the stacktrace from top
to bottom.
Maybe after logout you redirect to a stateful page and Wicket needs to
create a new Session to store that page ...
On Thu, Feb 21, 2019 at 10:21 AM
As I encountered the same problem as AliKhan, I follow Martin's suggestion
to upgrade the wicket version from 7.10 to 7.12. However, I still go to the
following code inside the bind() method when the session is invalidate.
// explicitly create a session
24 matches
Mail list logo
