On Sep 15, 2005, at 4:17 PM, Tore Halset wrote:
> This is the way I was thinking..:
> * The objects and the object graph are edited on the client side
> using the client classes.
> * The client calls commit
> * The client logic sends the diff to the server context
> * The server propagates the info to the server classes. If person's
> fullName changed on the server, call Person.setFullName with the
> new value on the server.
> * The server context commit
Yeah, that's how I thought it would work.
> It should be possible for the app developer to have some logic in
> the server classes and some other logic on the client classes.
What I am still unclear is a very simple case below. Consider this
method called from UI (web or Swing), not on commit:
public String getUrl() {
return getPart1() + getPart2() + getPart3();
}
I am trying to avoid duplication of this code between client and
server classes. I guess inheritance of server objects from client
objects would be an option...
Andrus
This archive was generated by hypermail 2.0.0 : Thu Sep 15 2005 - 16:30:52 EDT