Re: GWT Serialization issue with detachable JDO class
Unfortunately, the GWT serialization process is not really neither documented nor extensible :-( I opened a RFE about it (http://code.google.com/p/google-web-toolkit/ issues/detail?id=1291&can=1), but it is still marked as new an no one seems to care about it. That's why the solution implemented on Gilead seems to me the only one compatible without modifying GWT source code. Note that BlazeDS (the serialization library for Flex framework) has been *thought* to be extensible and provides extensions points with adapters and factory concept. I would really hope that GWT developers will be inspired by it when they will refactor the RPC serialization process. Regards Bruno On 15 fév, 01:37, Prempena wrote: > Yes, I've read in detail all the Gilead documentation and also tried > the examples. Good job indeed! But it is a pity to have to duplicate > an object already available to be used at the client side, just > because of serialization issues. We should be able to customize the > GWT serialization process in order to have a completely opened data > transfer between the server and the client. Do you know if there is > some detailed documentation about the GWT serialization? > > On 14 fév, 21:07, noon wrote: > > > Hi, > > > It really looks like similar issues with Hibernate entities (failure > > on GWT serialization). > > The solution I implemented on Gilead library (http:// > > gilead.sourceforge.net) is based on beanlib, that clones your entities > > to make them acceptable to GWT serializer. > > > Hope this helps > > Bruno > > > On 14 fév, 13:18, Prempena wrote: > > > > Hi, > > > > I would like to be able to use JDO objects, persisted by Datanucleus, > > > directly in the GWT client, after the class has been serialized from > > > the server to the client via the GWT serialization mechanism. > > > > It works fine when working with transient JDO objects. I'm able to > > > move the object back and forth between the client and the server > > > without any issue. > > > > Unfortunately, when the class is tagged as detachable (with the goal > > > to allow the update of the object in the datastore when coming back to > > > the server), the GWT Serialization doesn't work, due to some objects > > > added by the enhancement process: Object[] jdoDetachedState. > > > > Of course, I would like to avoid JDO Object copy to a POJO > > > serializable by GWT: it is waste of time and painful to do. > > > > Any Idea to help me to find a solution or a workaround to solve this > > > issue? > > > > Thanks in advance,- Masquer le texte des messages précédents - > > > - Afficher le texte des messages précédents - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT Serialization issue with detachable JDO class
Yes, I've read in detail all the Gilead documentation and also tried the examples. Good job indeed! But it is a pity to have to duplicate an object already available to be used at the client side, just because of serialization issues. We should be able to customize the GWT serialization process in order to have a completely opened data transfer between the server and the client. Do you know if there is some detailed documentation about the GWT serialization? On 14 fév, 21:07, noon wrote: > Hi, > > It really looks like similar issues with Hibernate entities (failure > on GWT serialization). > The solution I implemented on Gilead library (http:// > gilead.sourceforge.net) is based on beanlib, that clones your entities > to make them acceptable to GWT serializer. > > Hope this helps > Bruno > > On 14 fév, 13:18, Prempena wrote: > > > > > Hi, > > > I would like to be able to use JDO objects, persisted by Datanucleus, > > directly in the GWT client, after the class has been serialized from > > the server to the client via the GWT serialization mechanism. > > > It works fine when working with transient JDO objects. I'm able to > > move the object back and forth between the client and the server > > without any issue. > > > Unfortunately, when the class is tagged as detachable (with the goal > > to allow the update of the object in the datastore when coming back to > > the server), the GWT Serialization doesn't work, due to some objects > > added by the enhancement process: Object[] jdoDetachedState. > > > Of course, I would like to avoid JDO Object copy to a POJO > > serializable by GWT: it is waste of time and painful to do. > > > Any Idea to help me to find a solution or a workaround to solve this > > issue? > > > Thanks in advance,- Masquer le texte des messages précédents - > > - Afficher le texte des messages précédents - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT Serialization issue with detachable JDO class
Hi, It really looks like similar issues with Hibernate entities (failure on GWT serialization). The solution I implemented on Gilead library (http:// gilead.sourceforge.net) is based on beanlib, that clones your entities to make them acceptable to GWT serializer. Hope this helps Bruno On 14 fév, 13:18, Prempena wrote: > Hi, > > I would like to be able to use JDO objects, persisted by Datanucleus, > directly in the GWT client, after the class has been serialized from > the server to the client via the GWT serialization mechanism. > > It works fine when working with transient JDO objects. I'm able to > move the object back and forth between the client and the server > without any issue. > > Unfortunately, when the class is tagged as detachable (with the goal > to allow the update of the object in the datastore when coming back to > the server), the GWT Serialization doesn't work, due to some objects > added by the enhancement process: Object[] jdoDetachedState. > > Of course, I would like to avoid JDO Object copy to a POJO > serializable by GWT: it is waste of time and painful to do. > > Any Idea to help me to find a solution or a workaround to solve this > issue? > > Thanks in advance, --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
GWT Serialization issue with detachable JDO class
Hi, I would like to be able to use JDO objects, persisted by Datanucleus, directly in the GWT client, after the class has been serialized from the server to the client via the GWT serialization mechanism. It works fine when working with transient JDO objects. I'm able to move the object back and forth between the client and the server without any issue. Unfortunately, when the class is tagged as detachable (with the goal to allow the update of the object in the datastore when coming back to the server), the GWT Serialization doesn't work, due to some objects added by the enhancement process: Object[] jdoDetachedState. Of course, I would like to avoid JDO Object copy to a POJO serializable by GWT: it is waste of time and painful to do. Any Idea to help me to find a solution or a workaround to solve this issue? Thanks in advance, --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
