Re: Wicket's error message-> java.lang.IllegalStateException: This container is already dequeing
PrescientTemplateOriginalPage is actually the parent class of PrescientHome so that why PrescientTemplateOriginalPage had the tag, and prescientHome had the . I was able to solve the problem and your assistance was greatly appreciated. The problem is seems was how I was referring my form id. I needed to put and not . Francois thank you so much for all your assistance. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket's error message-> java.lang.IllegalStateException: This container is already dequeing
I don't think I have the privileges to do but let Martin Tzvetanov Grigorov know to close the issue on Jira. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Retrieve user's page on the site
In our experience these can be a mixed bag of expired requests, expired links, incorrect back button presses (and links from stale pages), session timeouts, etc. We haven't been able to trace them either, if a solution exists, I wish it was part of wicket core. Using more human readable urls might help, identifying session and clicked button and maybe page state, which could be later backtraced to determine any inconsistencies. ** Martin ma 30. jouluk. 2019 klo 6.24 Илья Нарыжный (phan...@ydn.ru) kirjoitti: > Hello, > > We have pretty widely used software with thousands of visits per day. > And from time to time we observe pretty weird Wicket related errors > in logs. Commonly it's something about components structure: no such > child, there is already such element and etc. But the problem is that > commonly we can't reproduce the problem right away: page is working as > expected. So such mysterious problems just lie in logs and not being > fixed. > And here is the question: is there some good way to retrieve and log > previous user actions and etc.? Theoretically everything should be in > PageStore. What can you recommend to handle such problems properly? > > P.S. To be able to catch such problems we even build a system for > gathering all logs on a central server and correlate them with each > other according to some correlation logic. But still - no big luck - > so we really believe that problem is in fact that we know only current > user page/location and do not know historical aspect. > > Thanks, > Ilia > > - > Orienteer(http://orienteer.org) - open source Business Application > Platform > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Retrieve user's page on the site
Hello, We have pretty widely used software with thousands of visits per day. And from time to time we observe pretty weird Wicket related errors in logs. Commonly it's something about components structure: no such child, there is already such element and etc. But the problem is that commonly we can't reproduce the problem right away: page is working as expected. So such mysterious problems just lie in logs and not being fixed. And here is the question: is there some good way to retrieve and log previous user actions and etc.? Theoretically everything should be in PageStore. What can you recommend to handle such problems properly? P.S. To be able to catch such problems we even build a system for gathering all logs on a central server and correlate them with each other according to some correlation logic. But still - no big luck - so we really believe that problem is in fact that we know only current user page/location and do not know historical aspect. Thanks, Ilia - Orienteer(http://orienteer.org) - open source Business Application Platform - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket's error message-> java.lang.IllegalStateException: This container is already dequeing
Please, if you manage to solve your problem here in the mailing list remember to close WICKET-6721 on Jira. On 12/29/19 10:46 AM, francois meillet wrote: you are adding the header and the footer panels in the child page but the html tag is in the super class. François Le 28 déc. 2019 à 22:35, LSomefun a écrit : I do appreciate you looking at this while on holiday. The 2nd constructor of PrescientTemplateOriginalPage I have deleted. Truth is it was not needed. The HTML code of PrescientHome I initially submitted did not include the HeaderPanel and footerPanel, was because of inheritance from PrescientTemplateOriginalPage so did not need to include them. The HTML Code from PrescientTemplateOriginalPage is below Template And the HTML code from PrecientHome is below TODO supply a title Doctors : Choose one Physician Dentist Optometrist . -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Best way to refresh entire NestedTree
Hi Chris,
On Sun, Dec 29, 2019 at 11:22 AM Chris Colman
wrote:
> Sorry for the duplication. These messages did not appear in the mail
> group until about 8 hours after they were posted. I thought I must have
>
This is because you are not subscribed to the mailing list and your
messages are moderated.
> 'misdirected' the first one. Was there a problem with the mail group today?
>
> Anyway - I eventually worked out how to do it!
>
> The secret was in the source code of the TreeModelProvider class - which
> we don't use but it has a method called
>
> update(AbstractTree tree, AjaxRequestTarget target)
>
> which did this magic (among other things):
>
> ...
> if (completeUpdate)
> target.add(new Componen[]{tree});
> ...
> this,detach();
>
>
> So I added a similar method, called completeUpdate, to pagebloom's own
> ITreeProvider implementation, TreeNodeProvider and it all worked
> amazingly well, after adding some additional detachment of the root nodes.
>
>
>
>
> On 29/12/2019 2:09 pm, chrisco wrote:
> > I have a UI layout where selection changes in one component need to
> result in
> > a complete repopulation of the nodes in an associated NestedTree.
> >
> > Obviously I don't want to do a complete page refresh so I was wondering
> what
> > the best way is to do an AJAX refresh of the entire NestedTree after I've
> > told it, somehow, that all of its nodes need to be replaced.
> >
> > Is it as simple as just replacing the ITreeProvider and then adding the
> > NestedTree to the AJAX request target or is there something more
> involved?
> >
> > Merry Christmas/Holiday everyone,
> >
> > Regards,
> >
> > Chris
> >
> > --
> > Sent from:
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
>
Re: Best way to refresh entire NestedTree
Actually - it's even easier than what I did before.
So long as the ITreeProvider implement can change the source of its data
then all that's required is an target.add() on the tree component!
As per usual Wicket makes it really simple but I go looking for harder
solutions :)
On 29/12/2019 5:40 pm, Chris Colman wrote:
Sorry for the duplication. These messages did not appear in the mail
group until about 8 hours after they were posted. I thought I must
have 'misdirected' the first one. Was there a problem with the mail
group today?
Anyway - I eventually worked out how to do it!
The secret was in the source code of the TreeModelProvider class -
which we don't use but it has a method called
update(AbstractTree tree, AjaxRequestTarget target)
which did this magic (among other things):
...
if (completeUpdate)
target.add(new Componen[]{tree});
...
this,detach();
So I added a similar method, called completeUpdate, to pagebloom's own
ITreeProvider implementation, TreeNodeProvider and it all worked
amazingly well, after adding some additional detachment of the root
nodes.
On 29/12/2019 2:09 pm, chrisco wrote:
I have a UI layout where selection changes in one component need to
result in
a complete repopulation of the nodes in an associated NestedTree.
Obviously I don't want to do a complete page refresh so I was
wondering what
the best way is to do an AJAX refresh of the entire NestedTree after
I've
told it, somehow, that all of its nodes need to be replaced.
Is it as simple as just replacing the ITreeProvider and then adding the
NestedTree to the AJAX request target or is there something more
involved?
Merry Christmas/Holiday everyone,
Regards,
Chris
--
Sent from:
http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket's error message-> java.lang.IllegalStateException: This container is already dequeing
you are adding the header and the footer panels in the child page but the html tag is in the super class. François > Le 28 déc. 2019 à 22:35, LSomefun a écrit : > > I do appreciate you looking at this while on holiday. The 2nd constructor of > PrescientTemplateOriginalPage I have deleted. Truth is it was not needed. > The HTML code of PrescientHome I initially submitted did not include the > HeaderPanel and footerPanel, was because of inheritance from > PrescientTemplateOriginalPage so did not need to include them. > The HTML Code from PrescientTemplateOriginalPage is below > > >Template > > > > > > > > > > > > > > And the HTML code from PrecientHome is below > > >TODO supply a title > > > > > > > > > Doctors : > >Choose one >Physician >Dentist >Optometrist > >. > > > > > > > > -- > Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Best way to refresh entire NestedTree
Sorry for the duplication. These messages did not appear in the mail
group until about 8 hours after they were posted. I thought I must have
'misdirected' the first one. Was there a problem with the mail group today?
Anyway - I eventually worked out how to do it!
The secret was in the source code of the TreeModelProvider class - which
we don't use but it has a method called
update(AbstractTree tree, AjaxRequestTarget target)
which did this magic (among other things):
...
if (completeUpdate)
target.add(new Componen[]{tree});
...
this,detach();
So I added a similar method, called completeUpdate, to pagebloom's own
ITreeProvider implementation, TreeNodeProvider and it all worked
amazingly well, after adding some additional detachment of the root nodes.
On 29/12/2019 2:09 pm, chrisco wrote:
I have a UI layout where selection changes in one component need to result in
a complete repopulation of the nodes in an associated NestedTree.
Obviously I don't want to do a complete page refresh so I was wondering what
the best way is to do an AJAX refresh of the entire NestedTree after I've
told it, somehow, that all of its nodes need to be replaced.
Is it as simple as just replacing the ITreeProvider and then adding the
NestedTree to the AJAX request target or is there something more involved?
Merry Christmas/Holiday everyone,
Regards,
Chris
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
