Hi, Anders.
We're doing something "logically similar" to annotations, but since most of our mapping from Java to Neo is not direct (we have an entire metamodel that sits on top of a few generic Java classes), we don't use annotations, but instead a similar approach using type definitions that are also stored in Neo. These type definitions include "type" information at the property level, default values, etc. The persistence layer then uses this metadata when storing/retrieving entities from Neo. Works well, since there is no real "typing" of properties built into Neo at present. Rick -------- Original Message -------- Subject: Re: [Neo] getProperty and null... From: Anders Nawroth <and...@neotechnology.com> Date: Tue, January 05, 2010 5:57 am To: Neo user discussions <user@lists.neo4j.org> Hi! Mattias Ask: > that isn't set. Or maybe I feel that the default should be that your domain > logic/model should decide if your code should fail miserably, and not the > persistence. I think annotation systems on top of Neo4j, like jo4neo, could be a good place for handling things on this level. And the "raw" Neo4j components should then provide solid foundations for such extensions to build upon (and work well with different paradigms). Would be interesting to know how those that are creating annotation stuff around Neo4j do think about this issue? /anders -- Anders Nawroth [and...@neotechnology.com] GTalk, Skype: anders.nawroth Phone: +46 737 894 163 [1]http://neo4j.org/ [2]http://twitter.com/nawroth [3]http://www.anders.nawroth.se/ _______________________________________________ Neo mailing list User@lists.neo4j.org [4]https://lists.neo4j.org/mailman/listinfo/user References 1. http://neo4j.org/ 2. http://twitter.com/nawroth 3. http://www.anders.nawroth.se/ 4. https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
