well the way i did it and i am sure that this is not the optimal way. Since they dont want to use maven in here i had to create the package *.share.* on svn and share it by the gwt module and any other module/project that needs to use those classes. so when i ran eclipse and import it, it looks like a linked package.
regards, Rudolf Michael On Wed, Jul 21, 2010 at 3:28 PM, Vinicius Carvalho < viniciusccarva...@gmail.com> wrote: > Hi there! I'm starting a project and the candidate architecture will > be GWT 2.0.4 + Spring 3.0 + SpringGWTRPC + Hibernate 3.3 + Gilead. > > So far, the GWT project have been created and I'm integrating it with > spring. My first thought was to separate in two maven modules nested > in a main project: > > parent > - web > - services (spring services, daos, model) > > My only concern with this lies on the gilead and the domain objects. > From what I've seen so far, you need to inform gwt about you domain > classes in order to it be able to serialize it right? Considering > they'll be on a different jar, how can I do this? Create a separate > gwt module? > > Regards > > -- > 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-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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-tool...@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.
