openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prashant Bhat <prashant...@gmail.com>
Subject Re: OpenJPA Date Proxy serialization problem when using entities with GWT
Date Thu, 10 Mar 2011 17:01:03 GMT
Hi Jeremy,

I'm using version="2.0", verified it again now. And I tried the
Compatibility setting you mentioned, but the same exception was thrown.

If it helps in finding cause, I can create a simple GWT application, but it
may take some time for me!

Regards,
Prashant

On Thu, Mar 10, 2011 at 11:42 PM, Jeremy Bauer <techhusky@gmail.com> wrote:

> Prashant,
>
> According to the OpenJPA migration considerations documentation[1] section
> 1.1.5, clear()/close() will remove proxies automatically upon serialization
> if you have a version 2.0 persistence.xml.  If you are using a version 1.0
> persistence.xml setting this property should result in proxy removal:
>
>      <property name="openjpa.Compatibility"
> value="IgnoreDetachedStateFieldForProxySerialization=false"/>
>
> hth,
> -Jeremy
>
> [1]
>
> http://openjpa.apache.org/builds/latest/docs/manual/migration_considerations.html
>
> On Wed, Mar 9, 2011 at 9:13 PM, Prashant Bhat <prashant.mr@gmail.com>
> wrote:
>
> > Hi All,
> >
> > We're developing an application using OpenJpa 2.1, Spring-3.0.5 and
> > GWT-2.2.0. This integration works for all other types in the entity, but
> > fails for fields of type Date with the following exception:
> > --
> > com.google.gwt.user.client.rpc.SerializationException: Type
> > 'org.apache.openjpa.util.java$util$Date$proxy' was not included in the
> set
> > of types which can be serialized by this SerializationPolicy or its Class
> > object could not be loaded. For security purposes, this type will not be
> > serialized.: instance = Sat Dec 31 00:00:00 SGT 2011
> > --
> > I tried using DTO instead of using an entity directly, but when date
> > property is copied from Entity object to DTO, the same proxy will be set.
> > So
> > it doesn't work either.
> >
> > When searched, I found lot of references to detaching the entity to
> remove
> > all proxies needed by Jpa. It works, but this needs to be explicitly
> > called,
> > while the same works without calling this, in our Swing app which gets
> the
> > serialized objects through Spring Remoting. And also, as there're a lot
> of
> > DAOs already written, this is going to be major change.
> >
> > So, is there a openjpa configuration setting to use, so that all proxies
> > are
> > removed on em.close() ? I really appreciate any help to solve this.
> >
> > Thanks,
> > Prashant
> >
>

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