No annotation nor XML binding is necessary : mapping is defined through method references.
Thanks to a fluent API, Stalactite lets one define its entity graph, instead of spreading it all over entities by annotation for instance.
Moreover, since it only fetches data eagerly, you know exactly what will be loaded, hence masterizing graph inflation.
-
Stalactite only accesses your properties through reflection : it doesn't require bytecode enhancement libraries, and doesn't have PersistentBag.
-
You may also keep your business constructor and let Stalactite uses it while fetching data from database.
-
Your equals/hashCode doesn't need to rely on entity identifier, you're free to implement it with business rules because Stalatite only
relies on equals/hashCode while comparing Collection, which is one of the purpose of their implementation.
Stalactite is tested against
- HSQLDB,
- H2,
- PostgreSQL,
- MySQL,
- MariaDB