Thanks for the reply, gscholt. Plese see my reply below. Aaron
On Jun 17, 4:17 am, gscholt <[email protected]> wrote: > http://code.google.com/webtoolkit/doc/1.6/RefJreEmulation.html > Since GWT does not emulate a full JRE, it is quite likely that you can > not use a 3rd party library that uses non-emulated parts of the JRE, > even if you have the source available. In your case it will never work > because of the dependency on javax.*. > Any such code can not be converted to javascript, and therefor can not > be used on the client side. > Using it on the server side is always an option, you'll just need to > abstract the library in classes that do not contain serialized > references to non-emulated JRE code. How you implement this service, > through xml,json,gwt-rpc,whatever is not conceptually relevant, but > I'd guess just using the gwt-rpc would be most convenient, keeping all > code in java, without a secondary service representation. > > On Jun 16, 11:49 pm, Aaron <[email protected]> wrote: > > > Hi Everyone, > > > I'm new to GWT and I'm very excited to start using it in a large > > enterprise application I'm working on. I have inherited an existing > > domain model that is available to me in a jar. I can build that jar > > with the source code included as well. > > > Ideally, I'd love to be able to work with my domain objects when > > writing my GWT client code. I have discovered it is not as simple as I > > had hoped. > > > I went ahead and created a GWT module for my classes and inherited > > that module into my GWT project. > > > When building my GWT project, I received GWT compiler errors about not > > having source code available for a dependent library we use > > (com.vividsolutions.jts)... I can get the source if needed, so no big > > deal. > > > Then I got errors related to javax.xml.bind annotations used in our > > classes: 'The import javax.xml.bind cannot be resolved' and > > 'XmlAccessorType cannot be resolved to a type'. I'm having more > > trouble figuring out what the solution to that problem is. > > > Any suggestions on the specific issues I just mentioned would be > > greatly appreciated, but I'm also interested in getting your feedback > > on, at a high level, what is the best approach when integrating more > > complex classes into a GWT project? Is it possible and worth it to > > track down the source code for every dependency your project has? Are > > annotations in your classes a problem in GWT or is there a way to deal > > with that? Is it better to write some 'simple' versions of my domain > > classes for use with GWT and then write code to convert back and forth > > between the two? Or, is a Json or XML service the simplest? > > > Thanks for any comments you have. GWT is an exciting project and I > > know it will be well worth my time figure this out. > > > Aaron --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
