You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Evan Chooly <ev...@gmail.com> on 2007/11/27 17:01:45 UTC
only 1 version of page in the cache at a time?
We have a page that presents a report in which we can "drill down" into the
data. When this happens, we setResponsePage() back to a new instance of the
page with some different parameters and that all works dandy. But when we
hit the back button, it seems the old version is gone. All the model data
comes back null (though the model object itself is not). So when we click
back and then click another link to drilldown in another direction we get
NPEs. From stepping through DiskPageStore, et. al, it would appear that
since the page class isn't changing, the new page bumps the old one from the
cache so that only one version of the page.
Am I correctly interpreting what I'm seeing and is there a way to set the
number of versions of a page?
Re: only 1 version of page in the cache at a time?
Posted by Evan Chooly <ev...@gmail.com>.
Thanks for the tip, igor. i wasn't sure how to get at the serialization
code directly without going through all the page stuff as well.
(DetachedReport)Objects.cloneObject(report) does indeed return an empty
Report object so there's something not quite right there. At least now I
have a place i can focus on without having to worry about all the other
wicket layers. I'll let you know what I find out.
On Nov 27, 2007 2:36 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> run it through Objects.clone() and see what you get back
>
> -igor
>
>
> On Nov 27, 2007 11:35 AM, Evan Chooly <ev...@gmail.com> wrote:
> > Just a pojo. (that's right! i said it! pojo! pojo! pojo!) It does
> have
> > a baseclass annotated with @MappedSuperclass but that shouldn't cause
> any
> > problems. The object is created by calling new and is never touched by
> > hibernate.
> >
> >
> > On Nov 27, 2007 2:31 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> >
> > > what is this report object?
> > >
> > > -igor
> > >
> > >
> > > On Nov 27, 2007 11:27 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > Just about every field in my model object. Though it would appear
> that
> > > the
> > > > date object(s) is set to "now."
> > > >
> > > >
> > > > On Nov 27, 2007 2:23 PM, Johan Compagner <jc...@gmail.com>
> wrote:
> > > >
> > > > > But what field is then exactly null???
> > > > >
> > > > >
> > > > >
> > > > > On Nov 27, 2007 7:05 PM, Evan Chooly <ev...@gmail.com> wrote:
> > > > >
> > > > > > just something like:
> > > > > >
> > > > > > setModel(new CompoundPropertyModel(report));
> > > > > >
> > > > > > On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > ok, so the model is there, but the object inside it suddenly
> is
> > > null?
> > > > > > > what kind of model is it?
> > > > > > >
> > > > > > > -igor
> > > > > > >
> > > > > > >
> > > > > > > On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com>
> wrote:
> > > > > > > > No, they're "detached" versions which are basically clones
> so
> > > > > there's
> > > > > > no
> > > > > > > > hibernate proxies involved.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Nov 27, 2007 12:42 PM, Igor Vaynberg <
> igor.vaynberg@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > these objects are not by chance hibernate objects? because
> if
> > > you
> > > > > > > > > serialize and then deserialize all the collections come
> back
> > > as
> > > > > > empty
> > > > > > > > > standard jdk collections instead of hibernate proxies
> > > sometimes
> > > > > > > > >
> > > > > > > > > -igor
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Nov 27, 2007 8:49 AM, Evan Chooly <evanchooly@gmail.com
> >
> > > wrote:
> > > > > > > > > > No transient fields. Everything is serializable. We're
> > > storing
> > > > > > the
> > > > > > > > > > complete objects in the model for a number of reasons.
> When
> > > we
> > > > > > come
> > > > > > > > > back to
> > > > > > > > > > the page we have some object but the state is gone. I
> think
> > > > > it's
> > > > > > > > > because
> > > > > > > > > > we're redirecting back to the same page class/type so
> the
> > > old
> > > > > one
> > > > > > > gets
> > > > > > > > > > dumped. Probably what I'll have to do,then, is to build
> > > special
> > > > > > > > > subclasses
> > > > > > > > > > for the drilldown so that the page type changes on each
> > > step.
> > > > > > > Unless
> > > > > > > > > > there's some way to increment the number of versions per
> > > > > > pagemap...
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Nov 27, 2007 11:39 AM, Johan Compagner <
> > > jcompagner@gmail.com>
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Yes in wicket 1.3 there is only 1 active page per
> pagemap
> > > > > > > > > > >
> > > > > > > > > > > But it shouldn't matter where the page comes from. If
> it
> > > is
> > > > > > > serialized
> > > > > > > > > > > from
> > > > > > > > > > > disk
> > > > > > > > > > > or serialized in the session somehow by the container,
> You
> > > > > still
> > > > > > > > > should be
> > > > > > > > > > > able
> > > > > > > > > > > to fully construct all your data again in the objects.
> > > > > > > > > > >
> > > > > > > > > > > So what is suddenly null? All the transient fields?
> Why
> > > aren't
> > > > > > > those
> > > > > > > > > > > reloaded
> > > > > > > > > > > from a database or something?
> > > > > > > > > > >
> > > > > > > > > > > johan
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <
> evanchooly@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > We have a page that presents a report in which we
> can
> > > "drill
> > > > > > > down"
> > > > > > > > > into
> > > > > > > > > > > > the
> > > > > > > > > > > > data. When this happens, we setResponsePage() back
> to a
> > > new
> > > > > > > > > instance of
> > > > > > > > > > > > the
> > > > > > > > > > > > page with some different parameters and that all
> works
> > > > > dandy.
> > > > > > > But
> > > > > > > > > when
> > > > > > > > > > > we
> > > > > > > > > > > > hit the back button, it seems the old version is
> gone.
> > > All
> > > > > > the
> > > > > > > > > model
> > > > > > > > > > > data
> > > > > > > > > > > > comes back null (though the model object itself is
> not).
> > > So
> > > > > > > when we
> > > > > > > > > > > click
> > > > > > > > > > > > back and then click another link to drilldown in
> another
> > > > > > > direction
> > > > > > > > > we
> > > > > > > > > > > get
> > > > > > > > > > > > NPEs. From stepping through DiskPageStore, et. al,
> it
> > > would
> > > > > > > appear
> > > > > > > > > that
> > > > > > > > > > > > since the page class isn't changing, the new page
> bumps
> > > the
> > > > > > old
> > > > > > > one
> > > > > > > > > from
> > > > > > > > > > > > the
> > > > > > > > > > > > cache so that only one version of the page.
> > > > > > > > > > > >
> > > > > > > > > > > > Am I correctly interpreting what I'm seeing and is
> there
> > > a
> > > > > way
> > > > > > > to
> > > > > > > > > set
> > > > > > > > > > > the
> > > > > > > > > > > > number of versions of a page?
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > > > To unsubscribe, e-mail:
> users-unsubscribe@wicket.apache.org
> > > > > > > > > For additional commands, e-mail:
> users-help@wicket.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: only 1 version of page in the cache at a time?
Posted by Igor Vaynberg <ig...@gmail.com>.
run it through Objects.clone() and see what you get back
-igor
On Nov 27, 2007 11:35 AM, Evan Chooly <ev...@gmail.com> wrote:
> Just a pojo. (that's right! i said it! pojo! pojo! pojo!) It does have
> a baseclass annotated with @MappedSuperclass but that shouldn't cause any
> problems. The object is created by calling new and is never touched by
> hibernate.
>
>
> On Nov 27, 2007 2:31 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>
> > what is this report object?
> >
> > -igor
> >
> >
> > On Nov 27, 2007 11:27 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > Just about every field in my model object. Though it would appear that
> > the
> > > date object(s) is set to "now."
> > >
> > >
> > > On Nov 27, 2007 2:23 PM, Johan Compagner <jc...@gmail.com> wrote:
> > >
> > > > But what field is then exactly null???
> > > >
> > > >
> > > >
> > > > On Nov 27, 2007 7:05 PM, Evan Chooly <ev...@gmail.com> wrote:
> > > >
> > > > > just something like:
> > > > >
> > > > > setModel(new CompoundPropertyModel(report));
> > > > >
> > > > > On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com>
> > wrote:
> > > > >
> > > > > > ok, so the model is there, but the object inside it suddenly is
> > null?
> > > > > > what kind of model is it?
> > > > > >
> > > > > > -igor
> > > > > >
> > > > > >
> > > > > > On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > > > > No, they're "detached" versions which are basically clones so
> > > > there's
> > > > > no
> > > > > > > hibernate proxies involved.
> > > > > > >
> > > > > > >
> > > > > > > On Nov 27, 2007 12:42 PM, Igor Vaynberg <igor.vaynberg@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > these objects are not by chance hibernate objects? because if
> > you
> > > > > > > > serialize and then deserialize all the collections come back
> > as
> > > > > empty
> > > > > > > > standard jdk collections instead of hibernate proxies
> > sometimes
> > > > > > > >
> > > > > > > > -igor
> > > > > > > >
> > > > > > > >
> > > > > > > > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com>
> > wrote:
> > > > > > > > > No transient fields. Everything is serializable. We're
> > storing
> > > > > the
> > > > > > > > > complete objects in the model for a number of reasons. When
> > we
> > > > > come
> > > > > > > > back to
> > > > > > > > > the page we have some object but the state is gone. I think
> > > > it's
> > > > > > > > because
> > > > > > > > > we're redirecting back to the same page class/type so the
> > old
> > > > one
> > > > > > gets
> > > > > > > > > dumped. Probably what I'll have to do,then, is to build
> > special
> > > > > > > > subclasses
> > > > > > > > > for the drilldown so that the page type changes on each
> > step.
> > > > > > Unless
> > > > > > > > > there's some way to increment the number of versions per
> > > > > pagemap...
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Nov 27, 2007 11:39 AM, Johan Compagner <
> > jcompagner@gmail.com>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > > > > > > > > >
> > > > > > > > > > But it shouldn't matter where the page comes from. If it
> > is
> > > > > > serialized
> > > > > > > > > > from
> > > > > > > > > > disk
> > > > > > > > > > or serialized in the session somehow by the container, You
> > > > still
> > > > > > > > should be
> > > > > > > > > > able
> > > > > > > > > > to fully construct all your data again in the objects.
> > > > > > > > > >
> > > > > > > > > > So what is suddenly null? All the transient fields? Why
> > aren't
> > > > > > those
> > > > > > > > > > reloaded
> > > > > > > > > > from a database or something?
> > > > > > > > > >
> > > > > > > > > > johan
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <evanchooly@gmail.com
> > >
> > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > We have a page that presents a report in which we can
> > "drill
> > > > > > down"
> > > > > > > > into
> > > > > > > > > > > the
> > > > > > > > > > > data. When this happens, we setResponsePage() back to a
> > new
> > > > > > > > instance of
> > > > > > > > > > > the
> > > > > > > > > > > page with some different parameters and that all works
> > > > dandy.
> > > > > > But
> > > > > > > > when
> > > > > > > > > > we
> > > > > > > > > > > hit the back button, it seems the old version is gone.
> > All
> > > > > the
> > > > > > > > model
> > > > > > > > > > data
> > > > > > > > > > > comes back null (though the model object itself is not).
> > So
> > > > > > when we
> > > > > > > > > > click
> > > > > > > > > > > back and then click another link to drilldown in another
> > > > > > direction
> > > > > > > > we
> > > > > > > > > > get
> > > > > > > > > > > NPEs. From stepping through DiskPageStore, et. al, it
> > would
> > > > > > appear
> > > > > > > > that
> > > > > > > > > > > since the page class isn't changing, the new page bumps
> > the
> > > > > old
> > > > > > one
> > > > > > > > from
> > > > > > > > > > > the
> > > > > > > > > > > cache so that only one version of the page.
> > > > > > > > > > >
> > > > > > > > > > > Am I correctly interpreting what I'm seeing and is there
> > a
> > > > way
> > > > > > to
> > > > > > > > set
> > > > > > > > > > the
> > > > > > > > > > > number of versions of a page?
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: only 1 version of page in the cache at a time?
Posted by Johan Compagner <jc...@gmail.com>.
what happens if you just serialize that object your self and read it back
in?
It seems to me like a serializing problem for that object.
johan
On Nov 27, 2007 8:35 PM, Evan Chooly <ev...@gmail.com> wrote:
> Just a pojo. (that's right! i said it! pojo! pojo! pojo!) It does
> have
> a baseclass annotated with @MappedSuperclass but that shouldn't cause any
> problems. The object is created by calling new and is never touched by
> hibernate.
>
> On Nov 27, 2007 2:31 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>
> > what is this report object?
> >
> > -igor
> >
> >
> > On Nov 27, 2007 11:27 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > Just about every field in my model object. Though it would appear
> that
> > the
> > > date object(s) is set to "now."
> > >
> > >
> > > On Nov 27, 2007 2:23 PM, Johan Compagner <jc...@gmail.com> wrote:
> > >
> > > > But what field is then exactly null???
> > > >
> > > >
> > > >
> > > > On Nov 27, 2007 7:05 PM, Evan Chooly <ev...@gmail.com> wrote:
> > > >
> > > > > just something like:
> > > > >
> > > > > setModel(new CompoundPropertyModel(report));
> > > > >
> > > > > On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com>
> > wrote:
> > > > >
> > > > > > ok, so the model is there, but the object inside it suddenly is
> > null?
> > > > > > what kind of model is it?
> > > > > >
> > > > > > -igor
> > > > > >
> > > > > >
> > > > > > On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com>
> wrote:
> > > > > > > No, they're "detached" versions which are basically clones so
> > > > there's
> > > > > no
> > > > > > > hibernate proxies involved.
> > > > > > >
> > > > > > >
> > > > > > > On Nov 27, 2007 12:42 PM, Igor Vaynberg <
> igor.vaynberg@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > these objects are not by chance hibernate objects? because
> if
> > you
> > > > > > > > serialize and then deserialize all the collections come back
> > as
> > > > > empty
> > > > > > > > standard jdk collections instead of hibernate proxies
> > sometimes
> > > > > > > >
> > > > > > > > -igor
> > > > > > > >
> > > > > > > >
> > > > > > > > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com>
> > wrote:
> > > > > > > > > No transient fields. Everything is serializable. We're
> > storing
> > > > > the
> > > > > > > > > complete objects in the model for a number of reasons.
> When
> > we
> > > > > come
> > > > > > > > back to
> > > > > > > > > the page we have some object but the state is gone. I
> think
> > > > it's
> > > > > > > > because
> > > > > > > > > we're redirecting back to the same page class/type so the
> > old
> > > > one
> > > > > > gets
> > > > > > > > > dumped. Probably what I'll have to do,then, is to build
> > special
> > > > > > > > subclasses
> > > > > > > > > for the drilldown so that the page type changes on each
> > step.
> > > > > > Unless
> > > > > > > > > there's some way to increment the number of versions per
> > > > > pagemap...
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Nov 27, 2007 11:39 AM, Johan Compagner <
> > jcompagner@gmail.com>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Yes in wicket 1.3 there is only 1 active page per
> pagemap
> > > > > > > > > >
> > > > > > > > > > But it shouldn't matter where the page comes from. If it
> > is
> > > > > > serialized
> > > > > > > > > > from
> > > > > > > > > > disk
> > > > > > > > > > or serialized in the session somehow by the container,
> You
> > > > still
> > > > > > > > should be
> > > > > > > > > > able
> > > > > > > > > > to fully construct all your data again in the objects.
> > > > > > > > > >
> > > > > > > > > > So what is suddenly null? All the transient fields? Why
> > aren't
> > > > > > those
> > > > > > > > > > reloaded
> > > > > > > > > > from a database or something?
> > > > > > > > > >
> > > > > > > > > > johan
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <
> evanchooly@gmail.com
> > >
> > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > We have a page that presents a report in which we can
> > "drill
> > > > > > down"
> > > > > > > > into
> > > > > > > > > > > the
> > > > > > > > > > > data. When this happens, we setResponsePage() back to
> a
> > new
> > > > > > > > instance of
> > > > > > > > > > > the
> > > > > > > > > > > page with some different parameters and that all works
> > > > dandy.
> > > > > > But
> > > > > > > > when
> > > > > > > > > > we
> > > > > > > > > > > hit the back button, it seems the old version is gone.
> > All
> > > > > the
> > > > > > > > model
> > > > > > > > > > data
> > > > > > > > > > > comes back null (though the model object itself is
> not).
> > So
> > > > > > when we
> > > > > > > > > > click
> > > > > > > > > > > back and then click another link to drilldown in
> another
> > > > > > direction
> > > > > > > > we
> > > > > > > > > > get
> > > > > > > > > > > NPEs. From stepping through DiskPageStore, et. al, it
> > would
> > > > > > appear
> > > > > > > > that
> > > > > > > > > > > since the page class isn't changing, the new page
> bumps
> > the
> > > > > old
> > > > > > one
> > > > > > > > from
> > > > > > > > > > > the
> > > > > > > > > > > cache so that only one version of the page.
> > > > > > > > > > >
> > > > > > > > > > > Am I correctly interpreting what I'm seeing and is
> there
> > a
> > > > way
> > > > > > to
> > > > > > > > set
> > > > > > > > > > the
> > > > > > > > > > > number of versions of a page?
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > > For additional commands, e-mail:
> users-help@wicket.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: only 1 version of page in the cache at a time?
Posted by Evan Chooly <ev...@gmail.com>.
Just a pojo. (that's right! i said it! pojo! pojo! pojo!) It does have
a baseclass annotated with @MappedSuperclass but that shouldn't cause any
problems. The object is created by calling new and is never touched by
hibernate.
On Nov 27, 2007 2:31 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> what is this report object?
>
> -igor
>
>
> On Nov 27, 2007 11:27 AM, Evan Chooly <ev...@gmail.com> wrote:
> > Just about every field in my model object. Though it would appear that
> the
> > date object(s) is set to "now."
> >
> >
> > On Nov 27, 2007 2:23 PM, Johan Compagner <jc...@gmail.com> wrote:
> >
> > > But what field is then exactly null???
> > >
> > >
> > >
> > > On Nov 27, 2007 7:05 PM, Evan Chooly <ev...@gmail.com> wrote:
> > >
> > > > just something like:
> > > >
> > > > setModel(new CompoundPropertyModel(report));
> > > >
> > > > On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com>
> wrote:
> > > >
> > > > > ok, so the model is there, but the object inside it suddenly is
> null?
> > > > > what kind of model is it?
> > > > >
> > > > > -igor
> > > > >
> > > > >
> > > > > On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > > > No, they're "detached" versions which are basically clones so
> > > there's
> > > > no
> > > > > > hibernate proxies involved.
> > > > > >
> > > > > >
> > > > > > On Nov 27, 2007 12:42 PM, Igor Vaynberg <igor.vaynberg@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > these objects are not by chance hibernate objects? because if
> you
> > > > > > > serialize and then deserialize all the collections come back
> as
> > > > empty
> > > > > > > standard jdk collections instead of hibernate proxies
> sometimes
> > > > > > >
> > > > > > > -igor
> > > > > > >
> > > > > > >
> > > > > > > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com>
> wrote:
> > > > > > > > No transient fields. Everything is serializable. We're
> storing
> > > > the
> > > > > > > > complete objects in the model for a number of reasons. When
> we
> > > > come
> > > > > > > back to
> > > > > > > > the page we have some object but the state is gone. I think
> > > it's
> > > > > > > because
> > > > > > > > we're redirecting back to the same page class/type so the
> old
> > > one
> > > > > gets
> > > > > > > > dumped. Probably what I'll have to do,then, is to build
> special
> > > > > > > subclasses
> > > > > > > > for the drilldown so that the page type changes on each
> step.
> > > > > Unless
> > > > > > > > there's some way to increment the number of versions per
> > > > pagemap...
> > > > > > > >
> > > > > > > >
> > > > > > > > On Nov 27, 2007 11:39 AM, Johan Compagner <
> jcompagner@gmail.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > > > > > > > >
> > > > > > > > > But it shouldn't matter where the page comes from. If it
> is
> > > > > serialized
> > > > > > > > > from
> > > > > > > > > disk
> > > > > > > > > or serialized in the session somehow by the container, You
> > > still
> > > > > > > should be
> > > > > > > > > able
> > > > > > > > > to fully construct all your data again in the objects.
> > > > > > > > >
> > > > > > > > > So what is suddenly null? All the transient fields? Why
> aren't
> > > > > those
> > > > > > > > > reloaded
> > > > > > > > > from a database or something?
> > > > > > > > >
> > > > > > > > > johan
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <evanchooly@gmail.com
> >
> > > > wrote:
> > > > > > > > >
> > > > > > > > > > We have a page that presents a report in which we can
> "drill
> > > > > down"
> > > > > > > into
> > > > > > > > > > the
> > > > > > > > > > data. When this happens, we setResponsePage() back to a
> new
> > > > > > > instance of
> > > > > > > > > > the
> > > > > > > > > > page with some different parameters and that all works
> > > dandy.
> > > > > But
> > > > > > > when
> > > > > > > > > we
> > > > > > > > > > hit the back button, it seems the old version is gone.
> All
> > > > the
> > > > > > > model
> > > > > > > > > data
> > > > > > > > > > comes back null (though the model object itself is not).
> So
> > > > > when we
> > > > > > > > > click
> > > > > > > > > > back and then click another link to drilldown in another
> > > > > direction
> > > > > > > we
> > > > > > > > > get
> > > > > > > > > > NPEs. From stepping through DiskPageStore, et. al, it
> would
> > > > > appear
> > > > > > > that
> > > > > > > > > > since the page class isn't changing, the new page bumps
> the
> > > > old
> > > > > one
> > > > > > > from
> > > > > > > > > > the
> > > > > > > > > > cache so that only one version of the page.
> > > > > > > > > >
> > > > > > > > > > Am I correctly interpreting what I'm seeing and is there
> a
> > > way
> > > > > to
> > > > > > > set
> > > > > > > > > the
> > > > > > > > > > number of versions of a page?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: only 1 version of page in the cache at a time?
Posted by Igor Vaynberg <ig...@gmail.com>.
what is this report object?
-igor
On Nov 27, 2007 11:27 AM, Evan Chooly <ev...@gmail.com> wrote:
> Just about every field in my model object. Though it would appear that the
> date object(s) is set to "now."
>
>
> On Nov 27, 2007 2:23 PM, Johan Compagner <jc...@gmail.com> wrote:
>
> > But what field is then exactly null???
> >
> >
> >
> > On Nov 27, 2007 7:05 PM, Evan Chooly <ev...@gmail.com> wrote:
> >
> > > just something like:
> > >
> > > setModel(new CompoundPropertyModel(report));
> > >
> > > On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> > >
> > > > ok, so the model is there, but the object inside it suddenly is null?
> > > > what kind of model is it?
> > > >
> > > > -igor
> > > >
> > > >
> > > > On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > > No, they're "detached" versions which are basically clones so
> > there's
> > > no
> > > > > hibernate proxies involved.
> > > > >
> > > > >
> > > > > On Nov 27, 2007 12:42 PM, Igor Vaynberg <ig...@gmail.com>
> > > wrote:
> > > > >
> > > > > > these objects are not by chance hibernate objects? because if you
> > > > > > serialize and then deserialize all the collections come back as
> > > empty
> > > > > > standard jdk collections instead of hibernate proxies sometimes
> > > > > >
> > > > > > -igor
> > > > > >
> > > > > >
> > > > > > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > > > > No transient fields. Everything is serializable. We're storing
> > > the
> > > > > > > complete objects in the model for a number of reasons. When we
> > > come
> > > > > > back to
> > > > > > > the page we have some object but the state is gone. I think
> > it's
> > > > > > because
> > > > > > > we're redirecting back to the same page class/type so the old
> > one
> > > > gets
> > > > > > > dumped. Probably what I'll have to do,then, is to build special
> > > > > > subclasses
> > > > > > > for the drilldown so that the page type changes on each step.
> > > > Unless
> > > > > > > there's some way to increment the number of versions per
> > > pagemap...
> > > > > > >
> > > > > > >
> > > > > > > On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com>
> > > > wrote:
> > > > > > >
> > > > > > > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > > > > > > >
> > > > > > > > But it shouldn't matter where the page comes from. If it is
> > > > serialized
> > > > > > > > from
> > > > > > > > disk
> > > > > > > > or serialized in the session somehow by the container, You
> > still
> > > > > > should be
> > > > > > > > able
> > > > > > > > to fully construct all your data again in the objects.
> > > > > > > >
> > > > > > > > So what is suddenly null? All the transient fields? Why aren't
> > > > those
> > > > > > > > reloaded
> > > > > > > > from a database or something?
> > > > > > > >
> > > > > > > > johan
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com>
> > > wrote:
> > > > > > > >
> > > > > > > > > We have a page that presents a report in which we can "drill
> > > > down"
> > > > > > into
> > > > > > > > > the
> > > > > > > > > data. When this happens, we setResponsePage() back to a new
> > > > > > instance of
> > > > > > > > > the
> > > > > > > > > page with some different parameters and that all works
> > dandy.
> > > > But
> > > > > > when
> > > > > > > > we
> > > > > > > > > hit the back button, it seems the old version is gone. All
> > > the
> > > > > > model
> > > > > > > > data
> > > > > > > > > comes back null (though the model object itself is not). So
> > > > when we
> > > > > > > > click
> > > > > > > > > back and then click another link to drilldown in another
> > > > direction
> > > > > > we
> > > > > > > > get
> > > > > > > > > NPEs. From stepping through DiskPageStore, et. al, it would
> > > > appear
> > > > > > that
> > > > > > > > > since the page class isn't changing, the new page bumps the
> > > old
> > > > one
> > > > > > from
> > > > > > > > > the
> > > > > > > > > cache so that only one version of the page.
> > > > > > > > >
> > > > > > > > > Am I correctly interpreting what I'm seeing and is there a
> > way
> > > > to
> > > > > > set
> > > > > > > > the
> > > > > > > > > number of versions of a page?
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: only 1 version of page in the cache at a time?
Posted by Evan Chooly <ev...@gmail.com>.
Just about every field in my model object. Though it would appear that the
date object(s) is set to "now."
On Nov 27, 2007 2:23 PM, Johan Compagner <jc...@gmail.com> wrote:
> But what field is then exactly null???
>
>
>
> On Nov 27, 2007 7:05 PM, Evan Chooly <ev...@gmail.com> wrote:
>
> > just something like:
> >
> > setModel(new CompoundPropertyModel(report));
> >
> > On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> >
> > > ok, so the model is there, but the object inside it suddenly is null?
> > > what kind of model is it?
> > >
> > > -igor
> > >
> > >
> > > On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > No, they're "detached" versions which are basically clones so
> there's
> > no
> > > > hibernate proxies involved.
> > > >
> > > >
> > > > On Nov 27, 2007 12:42 PM, Igor Vaynberg <ig...@gmail.com>
> > wrote:
> > > >
> > > > > these objects are not by chance hibernate objects? because if you
> > > > > serialize and then deserialize all the collections come back as
> > empty
> > > > > standard jdk collections instead of hibernate proxies sometimes
> > > > >
> > > > > -igor
> > > > >
> > > > >
> > > > > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > > > No transient fields. Everything is serializable. We're storing
> > the
> > > > > > complete objects in the model for a number of reasons. When we
> > come
> > > > > back to
> > > > > > the page we have some object but the state is gone. I think
> it's
> > > > > because
> > > > > > we're redirecting back to the same page class/type so the old
> one
> > > gets
> > > > > > dumped. Probably what I'll have to do,then, is to build special
> > > > > subclasses
> > > > > > for the drilldown so that the page type changes on each step.
> > > Unless
> > > > > > there's some way to increment the number of versions per
> > pagemap...
> > > > > >
> > > > > >
> > > > > > On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > > > > > >
> > > > > > > But it shouldn't matter where the page comes from. If it is
> > > serialized
> > > > > > > from
> > > > > > > disk
> > > > > > > or serialized in the session somehow by the container, You
> still
> > > > > should be
> > > > > > > able
> > > > > > > to fully construct all your data again in the objects.
> > > > > > >
> > > > > > > So what is suddenly null? All the transient fields? Why aren't
> > > those
> > > > > > > reloaded
> > > > > > > from a database or something?
> > > > > > >
> > > > > > > johan
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com>
> > wrote:
> > > > > > >
> > > > > > > > We have a page that presents a report in which we can "drill
> > > down"
> > > > > into
> > > > > > > > the
> > > > > > > > data. When this happens, we setResponsePage() back to a new
> > > > > instance of
> > > > > > > > the
> > > > > > > > page with some different parameters and that all works
> dandy.
> > > But
> > > > > when
> > > > > > > we
> > > > > > > > hit the back button, it seems the old version is gone. All
> > the
> > > > > model
> > > > > > > data
> > > > > > > > comes back null (though the model object itself is not). So
> > > when we
> > > > > > > click
> > > > > > > > back and then click another link to drilldown in another
> > > direction
> > > > > we
> > > > > > > get
> > > > > > > > NPEs. From stepping through DiskPageStore, et. al, it would
> > > appear
> > > > > that
> > > > > > > > since the page class isn't changing, the new page bumps the
> > old
> > > one
> > > > > from
> > > > > > > > the
> > > > > > > > cache so that only one version of the page.
> > > > > > > >
> > > > > > > > Am I correctly interpreting what I'm seeing and is there a
> way
> > > to
> > > > > set
> > > > > > > the
> > > > > > > > number of versions of a page?
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
Re: only 1 version of page in the cache at a time?
Posted by Johan Compagner <jc...@gmail.com>.
But what field is then exactly null???
On Nov 27, 2007 7:05 PM, Evan Chooly <ev...@gmail.com> wrote:
> just something like:
>
> setModel(new CompoundPropertyModel(report));
>
> On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>
> > ok, so the model is there, but the object inside it suddenly is null?
> > what kind of model is it?
> >
> > -igor
> >
> >
> > On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > No, they're "detached" versions which are basically clones so there's
> no
> > > hibernate proxies involved.
> > >
> > >
> > > On Nov 27, 2007 12:42 PM, Igor Vaynberg <ig...@gmail.com>
> wrote:
> > >
> > > > these objects are not by chance hibernate objects? because if you
> > > > serialize and then deserialize all the collections come back as
> empty
> > > > standard jdk collections instead of hibernate proxies sometimes
> > > >
> > > > -igor
> > > >
> > > >
> > > > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > > No transient fields. Everything is serializable. We're storing
> the
> > > > > complete objects in the model for a number of reasons. When we
> come
> > > > back to
> > > > > the page we have some object but the state is gone. I think it's
> > > > because
> > > > > we're redirecting back to the same page class/type so the old one
> > gets
> > > > > dumped. Probably what I'll have to do,then, is to build special
> > > > subclasses
> > > > > for the drilldown so that the page type changes on each step.
> > Unless
> > > > > there's some way to increment the number of versions per
> pagemap...
> > > > >
> > > > >
> > > > > On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com>
> > wrote:
> > > > >
> > > > > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > > > > >
> > > > > > But it shouldn't matter where the page comes from. If it is
> > serialized
> > > > > > from
> > > > > > disk
> > > > > > or serialized in the session somehow by the container, You still
> > > > should be
> > > > > > able
> > > > > > to fully construct all your data again in the objects.
> > > > > >
> > > > > > So what is suddenly null? All the transient fields? Why aren't
> > those
> > > > > > reloaded
> > > > > > from a database or something?
> > > > > >
> > > > > > johan
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com>
> wrote:
> > > > > >
> > > > > > > We have a page that presents a report in which we can "drill
> > down"
> > > > into
> > > > > > > the
> > > > > > > data. When this happens, we setResponsePage() back to a new
> > > > instance of
> > > > > > > the
> > > > > > > page with some different parameters and that all works dandy.
> > But
> > > > when
> > > > > > we
> > > > > > > hit the back button, it seems the old version is gone. All
> the
> > > > model
> > > > > > data
> > > > > > > comes back null (though the model object itself is not). So
> > when we
> > > > > > click
> > > > > > > back and then click another link to drilldown in another
> > direction
> > > > we
> > > > > > get
> > > > > > > NPEs. From stepping through DiskPageStore, et. al, it would
> > appear
> > > > that
> > > > > > > since the page class isn't changing, the new page bumps the
> old
> > one
> > > > from
> > > > > > > the
> > > > > > > cache so that only one version of the page.
> > > > > > >
> > > > > > > Am I correctly interpreting what I'm seeing and is there a way
> > to
> > > > set
> > > > > > the
> > > > > > > number of versions of a page?
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: only 1 version of page in the cache at a time?
Posted by Evan Chooly <ev...@gmail.com>.
just something like:
setModel(new CompoundPropertyModel(report));
On Nov 27, 2007 1:04 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> ok, so the model is there, but the object inside it suddenly is null?
> what kind of model is it?
>
> -igor
>
>
> On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com> wrote:
> > No, they're "detached" versions which are basically clones so there's no
> > hibernate proxies involved.
> >
> >
> > On Nov 27, 2007 12:42 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> >
> > > these objects are not by chance hibernate objects? because if you
> > > serialize and then deserialize all the collections come back as empty
> > > standard jdk collections instead of hibernate proxies sometimes
> > >
> > > -igor
> > >
> > >
> > > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > > No transient fields. Everything is serializable. We're storing the
> > > > complete objects in the model for a number of reasons. When we come
> > > back to
> > > > the page we have some object but the state is gone. I think it's
> > > because
> > > > we're redirecting back to the same page class/type so the old one
> gets
> > > > dumped. Probably what I'll have to do,then, is to build special
> > > subclasses
> > > > for the drilldown so that the page type changes on each step.
> Unless
> > > > there's some way to increment the number of versions per pagemap...
> > > >
> > > >
> > > > On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com>
> wrote:
> > > >
> > > > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > > > >
> > > > > But it shouldn't matter where the page comes from. If it is
> serialized
> > > > > from
> > > > > disk
> > > > > or serialized in the session somehow by the container, You still
> > > should be
> > > > > able
> > > > > to fully construct all your data again in the objects.
> > > > >
> > > > > So what is suddenly null? All the transient fields? Why aren't
> those
> > > > > reloaded
> > > > > from a database or something?
> > > > >
> > > > > johan
> > > > >
> > > > >
> > > > >
> > > > > On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com> wrote:
> > > > >
> > > > > > We have a page that presents a report in which we can "drill
> down"
> > > into
> > > > > > the
> > > > > > data. When this happens, we setResponsePage() back to a new
> > > instance of
> > > > > > the
> > > > > > page with some different parameters and that all works dandy.
> But
> > > when
> > > > > we
> > > > > > hit the back button, it seems the old version is gone. All the
> > > model
> > > > > data
> > > > > > comes back null (though the model object itself is not). So
> when we
> > > > > click
> > > > > > back and then click another link to drilldown in another
> direction
> > > we
> > > > > get
> > > > > > NPEs. From stepping through DiskPageStore, et. al, it would
> appear
> > > that
> > > > > > since the page class isn't changing, the new page bumps the old
> one
> > > from
> > > > > > the
> > > > > > cache so that only one version of the page.
> > > > > >
> > > > > > Am I correctly interpreting what I'm seeing and is there a way
> to
> > > set
> > > > > the
> > > > > > number of versions of a page?
> > > > > >
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: only 1 version of page in the cache at a time?
Posted by Igor Vaynberg <ig...@gmail.com>.
ok, so the model is there, but the object inside it suddenly is null?
what kind of model is it?
-igor
On Nov 27, 2007 9:56 AM, Evan Chooly <ev...@gmail.com> wrote:
> No, they're "detached" versions which are basically clones so there's no
> hibernate proxies involved.
>
>
> On Nov 27, 2007 12:42 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>
> > these objects are not by chance hibernate objects? because if you
> > serialize and then deserialize all the collections come back as empty
> > standard jdk collections instead of hibernate proxies sometimes
> >
> > -igor
> >
> >
> > On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com> wrote:
> > > No transient fields. Everything is serializable. We're storing the
> > > complete objects in the model for a number of reasons. When we come
> > back to
> > > the page we have some object but the state is gone. I think it's
> > because
> > > we're redirecting back to the same page class/type so the old one gets
> > > dumped. Probably what I'll have to do,then, is to build special
> > subclasses
> > > for the drilldown so that the page type changes on each step. Unless
> > > there's some way to increment the number of versions per pagemap...
> > >
> > >
> > > On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com> wrote:
> > >
> > > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > > >
> > > > But it shouldn't matter where the page comes from. If it is serialized
> > > > from
> > > > disk
> > > > or serialized in the session somehow by the container, You still
> > should be
> > > > able
> > > > to fully construct all your data again in the objects.
> > > >
> > > > So what is suddenly null? All the transient fields? Why aren't those
> > > > reloaded
> > > > from a database or something?
> > > >
> > > > johan
> > > >
> > > >
> > > >
> > > > On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com> wrote:
> > > >
> > > > > We have a page that presents a report in which we can "drill down"
> > into
> > > > > the
> > > > > data. When this happens, we setResponsePage() back to a new
> > instance of
> > > > > the
> > > > > page with some different parameters and that all works dandy. But
> > when
> > > > we
> > > > > hit the back button, it seems the old version is gone. All the
> > model
> > > > data
> > > > > comes back null (though the model object itself is not). So when we
> > > > click
> > > > > back and then click another link to drilldown in another direction
> > we
> > > > get
> > > > > NPEs. From stepping through DiskPageStore, et. al, it would appear
> > that
> > > > > since the page class isn't changing, the new page bumps the old one
> > from
> > > > > the
> > > > > cache so that only one version of the page.
> > > > >
> > > > > Am I correctly interpreting what I'm seeing and is there a way to
> > set
> > > > the
> > > > > number of versions of a page?
> > > > >
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: only 1 version of page in the cache at a time?
Posted by Evan Chooly <ev...@gmail.com>.
No, they're "detached" versions which are basically clones so there's no
hibernate proxies involved.
On Nov 27, 2007 12:42 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> these objects are not by chance hibernate objects? because if you
> serialize and then deserialize all the collections come back as empty
> standard jdk collections instead of hibernate proxies sometimes
>
> -igor
>
>
> On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com> wrote:
> > No transient fields. Everything is serializable. We're storing the
> > complete objects in the model for a number of reasons. When we come
> back to
> > the page we have some object but the state is gone. I think it's
> because
> > we're redirecting back to the same page class/type so the old one gets
> > dumped. Probably what I'll have to do,then, is to build special
> subclasses
> > for the drilldown so that the page type changes on each step. Unless
> > there's some way to increment the number of versions per pagemap...
> >
> >
> > On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com> wrote:
> >
> > > Yes in wicket 1.3 there is only 1 active page per pagemap
> > >
> > > But it shouldn't matter where the page comes from. If it is serialized
> > > from
> > > disk
> > > or serialized in the session somehow by the container, You still
> should be
> > > able
> > > to fully construct all your data again in the objects.
> > >
> > > So what is suddenly null? All the transient fields? Why aren't those
> > > reloaded
> > > from a database or something?
> > >
> > > johan
> > >
> > >
> > >
> > > On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com> wrote:
> > >
> > > > We have a page that presents a report in which we can "drill down"
> into
> > > > the
> > > > data. When this happens, we setResponsePage() back to a new
> instance of
> > > > the
> > > > page with some different parameters and that all works dandy. But
> when
> > > we
> > > > hit the back button, it seems the old version is gone. All the
> model
> > > data
> > > > comes back null (though the model object itself is not). So when we
> > > click
> > > > back and then click another link to drilldown in another direction
> we
> > > get
> > > > NPEs. From stepping through DiskPageStore, et. al, it would appear
> that
> > > > since the page class isn't changing, the new page bumps the old one
> from
> > > > the
> > > > cache so that only one version of the page.
> > > >
> > > > Am I correctly interpreting what I'm seeing and is there a way to
> set
> > > the
> > > > number of versions of a page?
> > > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: only 1 version of page in the cache at a time?
Posted by Igor Vaynberg <ig...@gmail.com>.
these objects are not by chance hibernate objects? because if you
serialize and then deserialize all the collections come back as empty
standard jdk collections instead of hibernate proxies sometimes
-igor
On Nov 27, 2007 8:49 AM, Evan Chooly <ev...@gmail.com> wrote:
> No transient fields. Everything is serializable. We're storing the
> complete objects in the model for a number of reasons. When we come back to
> the page we have some object but the state is gone. I think it's because
> we're redirecting back to the same page class/type so the old one gets
> dumped. Probably what I'll have to do,then, is to build special subclasses
> for the drilldown so that the page type changes on each step. Unless
> there's some way to increment the number of versions per pagemap...
>
>
> On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com> wrote:
>
> > Yes in wicket 1.3 there is only 1 active page per pagemap
> >
> > But it shouldn't matter where the page comes from. If it is serialized
> > from
> > disk
> > or serialized in the session somehow by the container, You still should be
> > able
> > to fully construct all your data again in the objects.
> >
> > So what is suddenly null? All the transient fields? Why aren't those
> > reloaded
> > from a database or something?
> >
> > johan
> >
> >
> >
> > On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com> wrote:
> >
> > > We have a page that presents a report in which we can "drill down" into
> > > the
> > > data. When this happens, we setResponsePage() back to a new instance of
> > > the
> > > page with some different parameters and that all works dandy. But when
> > we
> > > hit the back button, it seems the old version is gone. All the model
> > data
> > > comes back null (though the model object itself is not). So when we
> > click
> > > back and then click another link to drilldown in another direction we
> > get
> > > NPEs. From stepping through DiskPageStore, et. al, it would appear that
> > > since the page class isn't changing, the new page bumps the old one from
> > > the
> > > cache so that only one version of the page.
> > >
> > > Am I correctly interpreting what I'm seeing and is there a way to set
> > the
> > > number of versions of a page?
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: only 1 version of page in the cache at a time?
Posted by Evan Chooly <ev...@gmail.com>.
No transient fields. Everything is serializable. We're storing the
complete objects in the model for a number of reasons. When we come back to
the page we have some object but the state is gone. I think it's because
we're redirecting back to the same page class/type so the old one gets
dumped. Probably what I'll have to do,then, is to build special subclasses
for the drilldown so that the page type changes on each step. Unless
there's some way to increment the number of versions per pagemap...
On Nov 27, 2007 11:39 AM, Johan Compagner <jc...@gmail.com> wrote:
> Yes in wicket 1.3 there is only 1 active page per pagemap
>
> But it shouldn't matter where the page comes from. If it is serialized
> from
> disk
> or serialized in the session somehow by the container, You still should be
> able
> to fully construct all your data again in the objects.
>
> So what is suddenly null? All the transient fields? Why aren't those
> reloaded
> from a database or something?
>
> johan
>
>
>
> On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com> wrote:
>
> > We have a page that presents a report in which we can "drill down" into
> > the
> > data. When this happens, we setResponsePage() back to a new instance of
> > the
> > page with some different parameters and that all works dandy. But when
> we
> > hit the back button, it seems the old version is gone. All the model
> data
> > comes back null (though the model object itself is not). So when we
> click
> > back and then click another link to drilldown in another direction we
> get
> > NPEs. From stepping through DiskPageStore, et. al, it would appear that
> > since the page class isn't changing, the new page bumps the old one from
> > the
> > cache so that only one version of the page.
> >
> > Am I correctly interpreting what I'm seeing and is there a way to set
> the
> > number of versions of a page?
> >
>
Re: only 1 version of page in the cache at a time?
Posted by Johan Compagner <jc...@gmail.com>.
Yes in wicket 1.3 there is only 1 active page per pagemap
But it shouldn't matter where the page comes from. If it is serialized from
disk
or serialized in the session somehow by the container, You still should be
able
to fully construct all your data again in the objects.
So what is suddenly null? All the transient fields? Why aren't those
reloaded
from a database or something?
johan
On Nov 27, 2007 5:01 PM, Evan Chooly <ev...@gmail.com> wrote:
> We have a page that presents a report in which we can "drill down" into
> the
> data. When this happens, we setResponsePage() back to a new instance of
> the
> page with some different parameters and that all works dandy. But when we
> hit the back button, it seems the old version is gone. All the model data
> comes back null (though the model object itself is not). So when we click
> back and then click another link to drilldown in another direction we get
> NPEs. From stepping through DiskPageStore, et. al, it would appear that
> since the page class isn't changing, the new page bumps the old one from
> the
> cache so that only one version of the page.
>
> Am I correctly interpreting what I'm seeing and is there a way to set the
> number of versions of a page?
>