What if the persistence layer is ejb for example?
Miroslav Genov wrote:
You don't have any problems to access client classes from server side
code. Just put all your model classes into client package
and use them in the persistence layer.
Kwhit wrote:
I'm building my first serious
From an architectural point of view I don't think it's very clean to
have classes that belong to the server side on the client side. Sooner
or later I'd regret it I'm sure. No, the more I play around, the more
I like the model I proposed. The OO model on the client side is likely
to be
Sharing classes on both the server and client has advantages and
disadvantages. Some of the advantages are that you don't have to
write special transport or serialization code to translate from server
to client objects. Another is that you can then write code that works
on both the client and
Think about performance too. If you have a bunch of unecessary data
being transferred across the wire your app will be slower.
On Jun 8, 1:25 am, Keith Whittingham kwhitting...@gmail.com wrote:
From an architectural point of view I don't think it's very clean to
have classes that belong to
How do you organize your gwt mvc application?
- gwt on the view
- some java pojos (or ejb3) on the model
- ?? on the controller
Considering that you have to show the first name, last name and e-mail
address and your User entity has many other fields, do you have a
service method getUserInfo that
Actually, GWT doesn't impose any requirements as to where you put your
source files, it just defaults to client. You just need to make
sure you have a GWT module.xml that references the specific
directories containing the files you want to include for the client
that the module represents.
I'm building my first serious GWT app and am looking for a 'template'
model to structure things. On the client side I need much the same
objects to populate the UI as on the server side to handle
persistence. Let's say I need Employee on the client side to edit
employee details and then I need
You don't have any problems to access client classes from server side
code. Just put all your model classes into client package
and use them in the persistence layer.
Kwhit wrote:
I'm building my first serious GWT app and am looking for a 'template'
model to structure things. On the client
