On Wed, Sep 9, 2009 at 5:35 PM, Thomas Holmes<[email protected]> wrote: > I get the idea that ouside packages need to be include in the module ... > but of course I am going to include code from outside packages .... > Hibernate and Spring jars are outside ... and there is no source code: > > so, here are some errors; > [ERROR] Line 5: The import org.springframework.orm cannot be resolved > [ERROR] Line 10: HibernateDaoSupport cannot be resolved to a type > [ERROR] Line 14: The method getHibernateTemplate() is undefined for the type > TestDaoImpl > > So, I added this to my StockWatcher.gwt.xml: > <!-- Other module inherits --> > <inherits > name='org.springframework.orm.hibernate3.support.HibernateDaoSupport'/> > > But now I get: > [TRACE] Loading inherited module > 'org.springframework.orm.hibernate3.support.HibernateDaoSupport' > [ERROR] Unable to find > 'org/springframework/orm/hibernate3/support/HibernateDaoSupport.gwt.xml' on > your classpath; > could be a typo, or maybe you forgot to include a classpath entry for > source? > > And then the application won't run at all ..
okay. you have to understand what crosscompiling actually means. the stuff you write in java for the gwt looks like java. eclipse even thinks it is java and the debugger works. but it is not java. so if it us no java. then you cannot include any java file. what is it then? well it is javascript. there is a really cool crosscompiling step involved that transforms the java stuff to javascript. so simply forget that you can include large java packages into your gwt application (btw => the spring package you included is not a gwt package => so this has to fails...). how to solve this? check out smart-gwt (http://code.google.com/p/smartgwt/) to get an idea (i don't know smart-gwt well, but the basic idea is cool). or generate some simple POJOs that have no dependencies to any package and can be handled by java server side code and also javascript code on the GWT client side. hope that helps... r > > On Wed, Sep 9, 2009 at 6:49 AM, Raphael André Bauer > <[email protected]> wrote: >> >> On Tue, Sep 8, 2009 at 10:17 PM, Thomas Holmes<[email protected]> >> wrote: >> > >> > Would you have some sample code that I could see ... or a link to >> > some. >> > >> > I'm going to continue looking through my book, and use their example >> > that uses the Command Pattern. >> > >> > I am getting tons of errors because my DAO's and POJO's are in another >> > package, so I was working with GWT Modules to try and make that work. >> > I finally gave that up and tried to move that code closer to the >> > Client directory ... and there a still a ton of errors. >> > >> > The most bothersome was in my UserDaoImpl where I have a >> > "getHibernateTemplate" method, and it says that the source code isn't >> > there. >> most likely this code is referenced by a module. some ideas: >> - check by which module it is referenced (if you have more than one) >> and make sure it is inherited by that module. >> - make sure it is under the /client/ directory, so that the gwt >> crosscompiler can find the sourcecode. >> - make sure the file has no external references (import xyz) that are >> not in the client directory >> >> this should make that part work... hope that helps... >> >> r >> >> >> >> >> >> > >> > So ... it is driving me crazy ... >> > >> > Thanks! >> > Tom >> > >> > On Sep 8, 4:04 pm, David Durham <[email protected]> wrote: >> >> > After research in this group, and on Google in general, I have found >> >> > that I should look at Gilead. >> >> > So, I downloaded the latest jars and the latest sample (using GWT >> >> > 1.6) >> >> > and sure enough, AGAIN, the sample uses hibernate.cfg.xml and >> >> > Object.hbm.xml files .... >> >> >> >> I was able to make GWT and Hiberate (JPA annotations) work without >> >> Gilead. I just used the underlying beanlib replicators to undo the >> >> cglib or javassist stuff before serializing to client. >> >> >> >> -Dave >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
