Pinaki, If the entities are detached, shouldn't we be serializing the non-proxy version of the various utility classes? For simple clients, we shouldn't require the use of the OpenJPA binaries, should we?
Kevin On Sun, Aug 3, 2008 at 10:39 PM, Pinaki Poddar <[EMAIL PROTECTED]> wrote: > > Hi, > > Looks like OpenJPA is subclassing the java.util.Date class so what's > passed is actually not the simple data type you're expecting but rather an > instance of org.apache.openjpa.util.java$util$Date$proxy > > You are right. OpenJPA proxies all mutable second class types [1] so that > any change in their state while they are remoted can be tracked and hence > can later be merged to a different persistence context. > > > > It looks like a dynamically generated class, > Yes. These proxy classes are dynamically generated. > > > It seems that they can not be passed over the remote interface. > > These dynamic proxies can be transmitted over the wire. If the remote > process has access to openjpa.jar then these classes should work as well in > the remote process without any explicit user level knowledge. > > > > Can i do anything to make it work?? > > The most obvious solution is to make openjpa.jar available to the Swing > client. > If that is not possible then consider custom proxy [2] [3]. > > [1] > > http://openjpa.apache.org/docs/latest/manual/manual.html#ref_guide_pc_scos_proxy_custom > [2] > > http://openjpa.apache.org/docs/latest/javadoc/org/apache/openjpa/util/ProxyManager.html > [3] > > http://openjpa.apache.org/docs/latest/javadoc/org/apache/openjpa/util/ProxyManagerImpl.html > > > -- > View this message in context: > http://n2.nabble.com/Re%3A-Is-java.util.date-not-supported-by-remote-interface---tp667769p667799.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. > >
