Hello,
I have found your project while was looking for a solution for a good concern
separation. You project looks awesome!
I have some questions which I was not able to derive in my own.
1. You suggest using generics Property<T> to define properties in the
application domain model. It seems there is one issue with this approach, which
I would like to clarify. Because of the type erasure, the underlying data type
is not available during run-time. Therefore the persistener, when loading an
instance from the storage, probably would not be able to verify if data loaded
matches corresponding data types in the model (this could happen because of
code refactoring, for example) and, presumably, this will lead to a class cast
exception in the application code. Such kind of issues will be difficult to
debug, since the error detection place is way far from the origin of the error.
Is this a relevant issue?
2. How would you suggest creating a unique constraint on a field with your
persistence schema?
3. If my application needs to query for, let say, all students not attending a
given course, how this can be done with your persistence schema?
Kind regards,
Eugene
P.S.
Sorry, the previous e-mail was sent by mistake from an intranet address. Please
do not reply to the sender if it was indeed distributed.
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
