On Mon, 30 Jun 2008, nate roe wrote:
> I'm now using Wicket 1.3.3 but I'm still seeing this behavior, where when my
> ListView is visited (from Form.loadPersistentFormComponentValues(),) my
> listView's children is null when it is visited in
> FormComponent.visitFormComponentsPostOrderHelper().
>
I'm now using Wicket 1.3.3 but I'm still seeing this behavior, where when my
ListView is visited (from Form.loadPersistentFormComponentValues(),) my
listView's children is null when it is visited in
FormComponent.visitFormComponentsPostOrderHelper().
It is difficult to understand why the ListView
On Wed, 11 Jun 2008, nate roe wrote:
> When exactly are ListView children created (or reused)?
Use the source, Luke! onBeforeRender AFAIK.
Best wishes,
Timo
--
Timo Rantalaiho
Reaktor Innovations Oyhttp://www.ri.fi/ >
-
Hrm. This issue may well be what I've run up against.
When exactly are ListView children created (or reused)?
On Tue, Jun 10, 2008 at 8:04 PM, Timo Rantalaiho <[EMAIL PROTECTED]>
wrote:
> On Tue, 10 Jun 2008, nate roe wrote:
> > Don't forget that I'm using 1.2... this has maybe changed and that
On Tue, 10 Jun 2008, nate roe wrote:
> Don't forget that I'm using 1.2... this has maybe changed and that's why
> Eclipse isn't showing the call hierarchy?
Before 1.3.0-beta3 there was trouble visiting repeater
children before they are rendered, could your problem be
caused by that?
http://is
That's called from Page.setFormComponentValuesFromCookies(...) which is in
turn called from .renderPage(...)
Don't forget that I'm using 1.2... this has maybe changed and that's why
Eclipse isn't showing the call hierarchy?
On Tue, Jun 10, 2008 at 5:19 PM, Igor Vaynberg <[EMAIL PROTECTED]>
wrote:
Form.loadPersisitentFormComponentValues()
-igor
On Tue, Jun 10, 2008 at 4:23 PM, nate roe <[EMAIL PROTECTED]> wrote:
> I'm sorry, which method do you mean?
>
> On Tue, Jun 10, 2008 at 4:02 PM, Igor Vaynberg <[EMAIL PROTECTED]>
> wrote:
>
>> what calls that method? call hieararchy for it is empty
I'm sorry, which method do you mean?
On Tue, Jun 10, 2008 at 4:02 PM, Igor Vaynberg <[EMAIL PROTECTED]>
wrote:
> what calls that method? call hieararchy for it is empty in
> eclipse...which is pretty strange...
>
> -igor
>
> On Tue, Jun 10, 2008 at 2:40 PM, nate roe <[EMAIL PROTECTED]> wrote:
> >
what calls that method? call hieararchy for it is empty in
eclipse...which is pretty strange...
-igor
On Tue, Jun 10, 2008 at 2:40 PM, nate roe <[EMAIL PROTECTED]> wrote:
> I can't figure out why Wicket is not calling
> Form.loadPersisitentFormComponentValues() for FormComponents that belong to
>
I can't figure out why Wicket is not calling
Form.loadPersisitentFormComponentValues() for FormComponents that belong to
a ListView.
Page.setFormComponentValuesFromCookies() calls visitChildren() inherited
from MarkupContainer. I can see that visitChildren() is called for my
ListView, but it look
form components inside listview are visited.
-igor
On Tue, Jun 10, 2008 at 1:40 PM, nate roe <[EMAIL PROTECTED]> wrote:
> I believe it's because a ListView is not a FormComponent, and the Form only
> visits its direct children. Does this sound plausible? How can I work
> around this to cause a
listview rebuilds its components in the beginning of each request.
setreuseitems inhibits that if the same page is redrawn, but if you
change the page the items are not preserved.
-igor
On Tue, Jun 10, 2008 at 1:37 PM, nate roe <[EMAIL PROTECTED]> wrote:
> I'm already using cookie names differen
I believe it's because a ListView is not a FormComponent, and the Form only
visits its direct children. Does this sound plausible? How can I work
around this to cause a Form's ListView's children to also be visited?
On Tue, Jun 10, 2008 at 1:37 PM, nate roe <[EMAIL PROTECTED]> wrote:
>
> I'm al
I'm already using cookie names different from the component IDs. It's just
that the components that belong to a ListView are never even checked for
loading.
Where does Wicket discard the ListView components when visiting its child
FormComponents?
On Tue, Jun 10, 2008 at 1:14 PM, Igor Vaynberg <[
i dont think cookie persistence is going to work for listviews out of
the box. the problem is that components inside repeaters do not have
stable component paths - and that is the key the cookie uses to store
values. so you will need to roll your own solution for this usecase.
-igor
On Tue, Jun 1
Yes, I have.
On Tue, Jun 10, 2008 at 11:48 AM, Timo Rantalaiho <[EMAIL PROTECTED]>
wrote:
> On Tue, 10 Jun 2008, nate roe wrote:
> > I have a form with several components. Some components are within a
> > ListView. Cookie value persistence does not appear to be loading values
> for
> > componen
On Tue, 10 Jun 2008, nate roe wrote:
> I have a form with several components. Some components are within a
> ListView. Cookie value persistence does not appear to be loading values for
> components in the ListView. I have a breakpoint in
> Form.loadPersistentFormComponentValues(...) at line 261:
I'm using Wicket 1.2.
I have a form with several components. Some components are within a
ListView. Cookie value persistence does not appear to be loading values for
components in the ListView. I have a breakpoint in
Form.loadPersistentFormComponentValues(...) at line 261:
if (
18 matches
Mail list logo
