On 21/09/11 12:37 PM, John Huss wrote:
I'm try to find out if I can make a single app that can work either with a
local DB or using ROP with a remote DB.
For the ObjectContext it looks like as long as the code uses the
ObjectContext interface that should allow to code to run against either and
there doesn't seem to be much loss of functionality from just using the
interface.
But for the entities it looks like the client should use PersistentObject
subclasses and the server should use CayenneDataObject subclasses, and
PersistentObject is missing some useful methods. So I'm wondering what in
CayenneDataObject prevents it from being used on the client, or what in
PersistentObject prevents it from being a good fit on the server. What is
the best way to end up with a single set of classes that supports both?
We have had the exact same issues and ended up with separate classes for client
and for server. And of course plenty of interfaces and helper classes to share
common business logic. We are also thinking about creating a single user
application with the server and client code merged into one application: when
we get around to that, I think the approach will be to continue to use ROP, but
short circuit the connection between client and server so it doesn't need to
travel over Hessian/Jetty. Hopefully we'll be working on that in a month or so.
Regards
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
