Flavio, The solution is essentially the same. I had assumed the classes you want to serialize are EntityBeans, but it sounds like they are Hibernate POJOs, but it's almost the same thing. The classes need to be "moduled" up and put on the GWT compiler classpath, they have to be "clean" with respect to JRE emulation, and since they are Hibernate objects, you will still have the lazy load proxy objects in there to contend with.
I think rolling your own XML serialization of these objects is a nightmare, don't do that. Walden On Sep 19, 10:03 am, "flavio faria" <[EMAIL PROTECTED]> wrote: > Thanks Wanden for your attention! > It's look like non-trivial way! > > Sorry but I don´t explain the solution completely. > > I use only Session Beans to implents bussiness logic and transaction context > and persistence with Hibernate. > > In this case the solution is the same? > > Do you no about one application with the same architecture? > > I was thinking about change my project. May be implements a middleware > broker to communicate with services under XML. > > What do you think about this solution? > > Have you another idea? > > Thanks > Flávio > > 2008/9/19 walden <[EMAIL PROTECTED]> > > > > > > > Yes, but it's not trivial. > > > First, you need to construct a gwt module around the ejb classes you > > intent to share with the client. This involves placing a > > <ejbname>.gwt.xml file someplace in the folder structure above all > > those classes, and then using the <source> tags to point to all the > > places where ejb sources live. This can sometimes force you to > > reorganize folders a little. None of this will work unless you are on > > GWT-1.5, by the way. > > > Next you need to see why the GWT compiler fails to compile your ejb > > sources. This is about dependencies that go outside your module and > > outside the GWT runtime emulation footprint. You'll have to rip all > > that out (and figure out how to live without it). > > > Finally, you will have to deal with runtime serialization problems > > wherein the JPA has replaced Java collections objects in your entities > > with its own persistence "lazy load" variants, which are not known to > > GWT and cannot be known to GWT and therefore cannot serialize. > > > Walden > > > On Sep 18, 5:31 pm, flavio <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I have been developing a client application with GWT to consume > > > services(EJB) to another application. > > > The client applications has a dependency with EJB app but when occurs > > > the RPC call i get the SerializationException error > > > > Caused by: com.google.gwt.user.client.rpc.SerializationException: Type > > > 'br.gov.trt.regiao1.basico.modelo.uf.dominio.UFDTO' was not included > > > in the set of types which can be serialized by this > > > SerializationPolicy. For security purposes, this type will not be > > > serialized. > > > > Where br.gov.trt.regiao1.basico.modelo.uf.dominio.UFDTO is an object > > > in the EJB app. > > > > Is it possible to develop GWT applications with this architecture? > > > > Thanks > > > Flávio- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
