cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nishant Neeraj <nishant.has.a.quest...@gmail.com>
Subject Re: Conditions when PersistenceState gets "hollow"
Date Thu, 01 Apr 2010 19:27:59 GMT
Thanks for the reply.
Yes, Wicket does serialize/de-serialize objects to/from session-store... so,
do I need to explicitly inflate the objects or there is a way to make sure
deserialization occurs properly?

Thanks
Nishant

On Fri, Apr 2, 2010 at 12:38 AM, Andrus Adamchik <andrus@objectstyle.org>wrote:

> I haven't used Wicket, but is there (de)serialization of objects involved
> when rendering a form and then submitting it back? This might result in
> turning an object to a hollow state. The last observation may be due to the
> object deserialized outside of its context...
>
> Andrus
>
>
> On Apr 1, 2010, at 9:28 PM, Nishant Neeraj wrote:
>
>  Also, when I "touch" (call getXXX) on the object it return empty string.
>>
>> On Thu, Apr 1, 2010 at 11:29 PM, Nishant Neeraj <nishant...@gmail.com
>> >wrote:
>>
>>  Hi,
>>>
>>> I am using Cayenne with Wicket.
>>>
>>> There are situations when I see object's persistence state HOLLOW.
>>> Specially, when I have committed something on a page, say by form
>>> submission, .... then clicked browser back button to come back to the
>>> same
>>> page and try to resubmit the form.
>>>
>>> The problem is, when resubmitting, instead of over-writing the same
>>> object.. it is trying to insert it in DB.. but since it has unique key
>>> that
>>> conflicts which previous commit, MySQL throws an exception.
>>>
>>> I wanted to know what are the situations when a data object is assigned
>>> HOLLOW?
>>>
>>>
>>> Thanks
>>> Nishant
>>>
>>>
>>>
>>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message