Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of michael.d.dick@gmail.com
 designates 209.85.218.46 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=A7Tl3qrCBC+zJpDxNbRYXWPguj6VleDeTVsFD0yDWt2JWfLg7JAOcgicBh5bW7z9xg
         DEEl3vVh0GU6YU/MH8cq6Nuc52EAKuqPxwuUvxFOPCdHj94L1fZ1rRQ6dILlMo59mklJ
         /jDwBCW0S/QbdCGheVKMuEwPQrrRSaLi1bFbM=
MIME-Version: 1.0
In-Reply-To: <AANLkTim5cM=S2MU0E_8uKY_+0+vc4h9DuVh4GFP_sD_q@mail.gmail.com>
References: <AANLkTinLW6yyn1QH-46F3VCsuJ1xyuCBuf68GcU8Hygr@mail.gmail.com>
 <AANLkTi=xmY6h3fF_kac-Bn7R8a-mbWMf4QKLQm4ca3yi@mail.gmail.com>
 <AANLkTinjeB1vu051b4cWMMDG97pizRqaXwNMOf4k+_h5@mail.gmail.com>
 <AANLkTi=RjjFETPasc7D2a3K2jNnfjt8PZsw6MVNbeRq_@mail.gmail.com>
 <AANLkTim5cM=S2MU0E_8uKY_+0+vc4h9DuVh4GFP_sD_q@mail.gmail.com>
From: Michael Dick <michael.d.dick@gmail.com>
Date: Thu, 24 Mar 2011 09:28:10 -0500
Message-ID: <AANLkTimRSvXGXeQfz9yMANvUJNQzzueNC748bViVw_12@mail.gmail.com>
Subject: Re: OpenJPA Date Proxy serialization problem when using entities with
 GWT
To: Prashant Bhat <prashant.mr@gmail.com>, dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=001485f8942495fa6e049f3b4ac5

--001485f8942495fa6e049f3b4ac5
Content-Type: text/plain; charset=ISO-8859-1

I agree.

What I'm aiming to do here is to give the application the option to remove
both the StateManager and proxies at a point that makes sense for their
application. For a lot of them removing the StateManager and proxies at
detach time will make sense. There's no way to do that right now though.

To answer Rick's question, the proxies delegate back to the StateManager to
dirty a field. If there's no SM they don't do anything, otherwise it's up to
the StateManager.

-mike

On Wed, Mar 23, 2011 at 8:57 PM, Prashant Bhat <prashant.mr@gmail.com>wrote:

> I don't know much about the benefits of using proxies, but in our
> particular usage, all proxies should be removed when the entity is
> detached/serialized. Then we can use entities directly in GWT avoiding DTOs
> and also with this, client side will not have dependency on OpenJPA at
> runtime.
>
> Regards,
> Prashant
>
>
> On Wed, Mar 23, 2011 at 9:22 PM, Michael Dick <michael.d.dick@gmail.com>wrote:
>
>> I haven't had a chance to look at your example application, but I think we
>> need to make some changes to the way we handle proxies.
>>
>> Currently there's no way to prevent proxies from being inserted. It's not
>> intuitive when they will be inserted, and they can be tough to remove.
>> What
>> I'd propose is to make it work something like this :
>>
>> if openjpa.ProxyManager.TrackChanges == False :
>>    # No proxies are inserted. Ever.
>>
>> else :
>>
>>    if openjpa.DetachState.DetachedStateField == "true":
>>        # proxies are inserted when the entity is flushed (or committed)
>>        # proxies are not removed when the entity is detached
>>        # proxies are not removed when the entity is serialized
>>
>>   elif openjpa.DetachState.DetachedStateField == "transient" :
>>        # proxies are inserted when the entity is flushed (or committed)
>>        # proxies are not removed when the entity is detached
>>        # proxies are removed when the entity is serialized
>>
>>    elif openjpa.DetachState.DetachedStateField == "false" :
>>        # proxies are inserted when the entity is flushed (or committed)
>>        # proxies are removed when the entity is detached
>>        # proxies are removed when the entity is serialized
>>
>> From what I've seen none of these are accurate for trunk, and the related
>> code path is a bit tangled (or I just haven't groked it).
>>
>> For your specific use case, would you want the proxies to ever be
>> inserted?
>>
>> -mike
>>
>>
>

--001485f8942495fa6e049f3b4ac5--