| Best practice using RCP with separate server [message #448378] |
Mon, 24 April 2006 08:40  |
Eclipse User |
|
|
|
Originally posted by: rdjohnson.kingwoodcable.com
Developing with RCP and a remote server (using Spring with remoting via RMI). When working with a domain object (for example, 'Customers'), is it best to define a Value Object on the RCP client side (i.e. CustomerVO), that sends and receives the customer properties? Then, when the domain object is to be validated/persisted, the VO could be passed back to a service on the server, for transformation to the domain object?
|
|
|
| Re: Best practice using RCP with separate server [message #448384 is a reply to message #448378] |
Mon, 24 April 2006 09:22  |
| Eclipse User |
|
|
|
It's a good question?
I my opnion it depends.
If it's your intention work on-line and off-line with a embedded database
like hsqldb for example, dont use VO, so you can work localy off-line and
syncronyze latter.
If you will use only on-line, maybe use http://xstream.codehaus.org/ or
other has some advantages couse you dont net update your plugins every time
your model changes and its cleaner than VOs.
But It's a problem that I'd like to see others opnios , since its a problem
that I have too.
"Randy Johnson" <rdjohnson@kingwoodcable.com> wrote in message
news:24436780.1145882446547.JavaMail.root@cp1.javalobby.org...
> Developing with RCP and a remote server (using Spring with remoting via
RMI). When working with a domain object (for example, 'Customers'), is it
best to define a Value Object on the RCP client side (i.e. CustomerVO), that
sends and receives the customer properties? Then, when the domain object is
to be validated/persisted, the VO could be passed back to a service on the
server, for transformation to the domain object?
|
|
|
Powered by
FUDForum. Page generated in 0.03340 seconds
Home