On Aug 15, 2007, at 7:17 PM, Aristedes Maniatis wrote:
Is it still a design goal to merge some of classes between client
and server, particularly the fact that objEntities have different
superclasses?
Yes it is. In fact POJO support on the server theoretically makes it
(almost?) possib
On 15/08/2007, at 11:11 PM, Andrus Adamchik wrote:
Ok, this is fixed - client side should now work as before.
I am also looking into making one-way to-many client relationships
updateable, just like they are on the server.
Andrus
Is it still a design goal to merge some of classes between
Ok, this is fixed - client side should now work as before.
I am also looking into making one-way to-many client relationships
updateable, just like they are on the server.
Andrus
On Aug 15, 2007, at 8:18 AM, Andrus Adamchik wrote:
Hmm... this may be a bug in implementation. "Runtime" rever
Hmm... this may be a bug in implementation. "Runtime" reverse
relationships (i.e. the relationships that Cayenne created on the
fly) would only work on CayenneDataObjects that can store arbitrary
stuff in the internal values map. Client side objects that use Java
fields to store properties
Hello
I think recently the requirement every relationship to be defined
both ways was revoked.
I found few problems with it:
we have defined (to many, read only):
deleteRule="Nullify" db-relationship-path="CourseClasses.sessions"/>
it looks like cayenne creates fake relationship called
run
