[
https://issues.apache.org/jira/browse/ISIS-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-1168:
------------------------------
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
was:
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
> Eagerly register entities with DataNucleus objectstore (for Neo4j)
> ------------------------------------------------------------------
>
> Key: ISIS-1168
> URL: https://issues.apache.org/jira/browse/ISIS-1168
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: core-1.8.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.9.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
