t; Not that it bothers me, since I never used custom DataSqueezers, but I
> think I understand Robert's confusion.
>
> -Vjeran
>
> - Original Message - From: "Ron Piterman" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesday, November 01, 2005 9:19 PM
> Subje
- Original Message -
From: "Ron Piterman" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, November 01, 2005 9:19 PM
Subject: Re: Persist large objects
I did not quite follow Henri's idea.
I would do exacly as you suggest- persist just the id and use it.
*maybe* that will work:
I did not quite follow Henri's idea.
I would do exacly as you suggest- persist just the id and use it.
*maybe* that will work:
public Object populateId(Object id) {
return ;
}
Cheers,
Ron
ציטוט Martin Strand:
Ok, does that mean that the best way is to persist the object id and
then s
I believe you could do that using a hivemind service and you could
inject in your hivemind service the object id value and put all your
methods in that object.
Henri.
On 11/1/05, Martin Strand <[EMAIL PROTECTED]> wrote:
> Ok, does that mean that the best way is to persist the object id and then
>
Ok, does that mean that the best way is to persist the object id and then
simply re-create the object myself on each request?
That's what I'm doing now, I just found that the same set of methods
(detach(), get/setSomeObject(), @Persist get/setSomeObjectId()) keeps
repeating itself in several
Ah, didn't know that, sorry... I'm curious as the motivation for /not/
using datasqueezers?
Robert
Howard Lewis Ship wrote:
> The client property persistent manager doesn't use the data squeezer;
> it always serializes a bunch of objects to a MIME64 stream. A
> DataSqueezer is used for objects e
The client property persistent manager doesn't use the data squeezer;
it always serializes a bunch of objects to a MIME64 stream. A
DataSqueezer is used for objects encoded as listener parameters or as
hidden form fields.
On 11/1/05, Robert Zeigler <[EMAIL PROTECTED]> wrote:
> Create a custom dat
Create a custom data squeezer for your object and register it.
Robert
Martin Strand wrote:
> Hi.
> I want to persist a large object on the client, but it would be much
> better if I could just persist its id and then re-create it on the
> server on each request. Can Tapestry do this for me? I c
