Ticket #818 (new enhancement)

Opened 9 months ago

Last modified 2 months ago

Change the Embedded class concept: instead of treating them as values ala Hibernate, treat them as Entities too.

Reported by: pradeep Assigned to: pradeep
Priority: high Milestone:
Component: topaz Version: 0.8.3-SNAPSHOT
Keywords: Cc:
Blocking: Blocked By:

Description

This is to enforce the notion that OTM only deals with sub-graphs as its 'atom' and more complex graphs can be built using inheritance, embedding and association.

Dependency Graph

Change History

03/22/08 03:40:52 changed by pradeep

(In [5141]) Refactor Mapper interface to reflect the fact that not all properties that OTM manages have a direct RDF persistence. So Mapper is the super interface that only contain a few properties common to all Mappers. The old Mapper is renamed as RdfMapper?. Additional Mapper sub-classes are Id, Blob, Embedded and OQL projections in a view.

Also ClassMetadata? now holds a list of Embedded Mappers. This made the OQL hacks via the POJO binders to get to the Embedded class disappear.

That leaves the View projection binding the only place that is POJO aware. (There is a bit of a chicken-and-egg situation here.) (See r4215, r4590, r4741, r4850 for the changes related to supporting non POJO bindings)

This also addresses #818. Embedded classes still are not treated as a form of multiple-inheritence yet.

03/31/08 16:14:28 changed by amit

  • milestone deleted.

More discussion needed here.

07/31/08 21:35:42 changed by amit

  • blocking changed.
  • blockedby changed.
  • milestone set to 0.9.1.

09/08/08 15:30:53 changed by amit

  • milestone deleted.