I actually *do* have that, but this code recently went through some ...
surgery that left things in a rather sloppy state. Clearly not the most
prize worthy section of code. :)
On Nov 27, 2007 10:43 PM, Timo Rantalaiho <[EMAIL PROTECTED]> wrote:
> On Tue, 27 Nov 2007, Evan Chooly wrote:
> > So
On Tue, 27 Nov 2007, Evan Chooly wrote:
> So here's the skinny: while my subclass was marked as serializable, the
> parent class was not. So no state from the parent class got serialized nor,
> not so surprisingly, deserialized. After adding that implements clause
> things miraculously started w
So here's the skinny: while my subclass was marked as serializable, the
parent class was not. So no state from the parent class got serialized nor,
not so surprisingly, deserialized. After adding that implements clause
things miraculously started working. So a big "you idiot" for me and a big
t
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 c
run it through Objects.clone() and see what you get back
-igor
On Nov 27, 2007 11:35 AM, Evan Chooly <[EMAIL PROTECTED]> 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.
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 <[EMAIL PROTECTED]> wrote:
> Just a pojo. (that's right! i said it! pojo! pojo! pojo!) It does
> have
> a
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 <[EMAIL PROTECTED]> wrote
what is this report object?
-igor
On Nov 27, 2007 11:27 AM, Evan Chooly <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote:
>
> > But w
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 <[EMAIL PROTECTED]> wrote:
> But what field is then exactly null???
>
>
>
> On Nov 27, 2007 7:05 PM, Evan Chooly <[EMAIL PROTECTED]> wrote:
>
> > ju
But what field is then exactly null???
On Nov 27, 2007 7:05 PM, Evan Chooly <[EMAIL PROTECTED]> wrote:
> just something like:
>
> setModel(new CompoundPropertyModel(report));
>
> On Nov 27, 2007 1:04 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> > ok, so the model is there, but the object in
just something like:
setModel(new CompoundPropertyModel(report));
On Nov 27, 2007 1:04 PM, Igor Vaynberg <[EMAIL PROTECTED]> 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 <[EMAIL PRO
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 <[EMAIL PROTECTED]> wrote:
> No, they're "detached" versions which are basically clones so there's no
> hibernate proxies involved.
>
>
> On Nov 27, 2007 12:
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 <[EMAIL PROTECTED]> wrote:
> these objects are not by chance hibernate objects? because if you
> serialize and then deserialize all the collections come bac
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 <[EMAIL PROTECTED]> wrote:
> No transient fields. Ev
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.
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 nul
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 d
17 matches
Mail list logo
