Hi Kevin,
Thanks for taking the time on this, and what you've implemented (or are
implementing) does look like the classic solution (as done in JDO, JPA
and also in NO.Net's layering on top of EF).
Since you seem to be making good progress, I'm going to keep on the
sidelines for now on this issue.
Cheers
Dan
On 03/09/2011 08:56, Kevin Meyer - KMZ wrote:
Dear all,
In trying to address Barry's problem, I have added simple support for
properties to be interfaces. See ISIS-117 and ISIS-118.
By storing the full concrete class name along with the Oid, the
following is now supported:
// {{ PolyInterface
private PolyInterface polyInterface;
public PolyInterface getPolyInterface() {
return polyInterface;
}
public void setPolyInterfaceType(final PolyInterface polyInterface) {
this.polyInterface = polyInterface;
}
// }}
where PolyInterface is an interface:
public interface PolyInterface {
}
An optimisaton might be to store a reference to a lookup table of full
class names instead of the full class name with every instance, but I
wanted to get the concept working, first.
I still don't have support for collections (even of interface), nor sub-
classed classes (the SQL-OS does not preserve properties of super-
classes, only the immediate properties of the subclassed class - so an
abstract super-class with no persisted properties, only actions, might
work, too ).
Regards,
Kevin
