[CAUSEWAY-1168] Eagerly register entities with DataNucleus objectstore (for Neo4j)

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: core-1.8.0
• Fix Version/s: 1.9.0
• Component/s: Core
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 06/Jul/15 06:21
• Updated: 01/Sep/15 19:49
• Resolved: 06/Jul/15 06:25

Description

The approach currently used (RegisterEntities to find all domain entities from classpath) does not seem to be working any more, seemingly because there are some (additional?) DN properties that also need to be specified when bootstrapping the DN PersistenceManagerFactory.

This is causing the isisaddons neoapp github.com/isisaddons/isis-app-neoapp) to incorrectly initialize.

see http://www.datanucleus.org/products/datanucleus/jdo/autostart.html

UPDATE: if attempt to eagerly register, then our MetadataListener does not fire for any auto-start entities. Have therefore reverted to only autoStart if connecting to Neo4j (ie, a hack).

Meantime, I have raised NUCCORE-1328 [1] and NUCCORE-1329 [2]; if first fixed then can go back to eagerly loading metadata for RDBMS, if second fixed then can get rid of Isis' implementation of creating the DB schema object and instead rely on DN.

[1] http://www.datanucleus.org/servlet/jira/browse/NUCCORE-1328
[2] http://www.datanucleus.org/servlet/jira/browse/NUCCORE-1329