Hi Denis, It is absolutely clear where domain object are NOT located, in client and shared. Domain objects have nothing to do in GUI or client
for a very simple project I would put it under server. But in general I would put domain objects into a separate project. The reason is, in general there is more than one application possible dealing the same domain objects. In general you have the following kind of objects on the server side which may build an own layer and thatfore projects. Session objects (state of your gui, application dependant, may be persistent) Application objects (application dependant, persistant) Domain objects (application independant, persistant) Stefan Bachert http://gwtworld.de On Jun 11, 10:45 pm, Denis <[email protected]> wrote: > Hello, > > I am new to use GWT RPC. > I am going to define a domain object which will map to a database > table and be transported all across the layers from the data > persistence to business logics and finally GWT presentation layer. > > The question is where should I define those domain objects? Inside the > existing client/server/shared folders or add a new domain folder? > > Thanks. > Denis -- 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.
