Like you, I read that it was possible but ran into the same issues. I ended up having to strip down the generated classes to POJO, which clearly reduces the advantages of using something like JAX-B in the first place. My understanding is that there are some classes in javax.xml that will never work correctly in GWT and that it was better to avoid it at all possible.
If anyone else wants to chime in and prove that we are wrong here, please feel free to do so. On Apr 20, 3:17 am, Stijn Bienkens <stijn.bienk...@k2-solutions.eu> wrote: > Hello > > We are currently looking to optimize some of our GWT projects but we > ran into a few issues. > > Most if not all of our data is coming from an OSGI backend. > Communication between the GWT client - GWT RPC - OSGI backend is far > from optimal as we have to write a lot of boiler plate code. To > optimize this we were thinking of including one ( or multiple) > webservices in our OSGI backend using Apache CXF. > > On the GWT RPC side we implemented a webservice client using Apache > CXF 2 as well. However the real challenge we are facing is how to use > the CXF generated objects for communication between GWT client and GWT > RPC. > > I've came across several posts claiming this was perfectly possible > but so far we haven't been successful. > > The Apache CXF generated classes have references to JAXBElement, when > compiling this results in: "No source code is available for type > javax.xml.bind.JAXBElement<T>;" > Using the <super-source> tag we provided the source for JAXBElement, > however this results in more of the same issues for: > javax.xml.namespace.Qname, java.io.ObjectInputStream, > java.lang.ClassNotFoundException, ... > > Is there anyway to accomplish this or another path we can follow? > > Thank you in advance > Stijn -- 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.
