Re: views created before tables?
Have you tried raising the DN logging levels? log4j.logger.DataNucleus.Datastore.Native=DEBUG, Console log4j.logger.DataNucleus.Datastore.Schema=DEBUG, Console Are all the entities the view uses being registered? Eg: are they in the same package as your AppManifest? On 8 November 2015 at 06:30, Stephen Cameronwrote: > seems to be the case, slightly annoying > > On Sun, Nov 8, 2015 at 3:10 PM, Stephen Cameron < > steve.cameron...@gmail.com> > wrote: > > > Hi, > > > > I am creating some database views via DataNucleus, but am getting some > > errors on startup of my webapp (with an clean database so all tables and > > views get greated). When I look at the new database schema via MySQL > > workbench I see the views have been created but not the tables, maybe > this > > is the origin of my errors. > > > > I cannot imagine why DN would do this, create views before creating > tables. > > > > org.datanucleus.exceptions.NucleusDataStoreException: An exception was > > thrown while adding/validating class(es) : Query was > > empty|com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Query > was > > empty<|?at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > > Method)<|?at > > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)<|?at > > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)<|?at > > java.lang.reflect.Constructor.newInstance(Constructor.java:422)<|?at > > com.mysql.jdbc.Util.handleNewInstance(Util.java:411)<|?at > > com.mysql.jdbc.Util.getInstance(Util.java:386)<|?at > > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)<|?at > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)<|?at > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)<|?at > > com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)<|?at > > com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)<|?at > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2619)<|?at > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2569)<|?at > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:824)<|?at > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:667)<|?at > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:879)<|?at > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:830)<|?at > > > org.datanucleus.store.rdbms.table.AbstractTable.create(AbstractTable.java:546)<|?at > > > org.datanucleus.store.rdbms.table.AbstractTable.exists(AbstractTable.java:609)<|?at > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.performViewsValidation(RDBMSStoreManager.java:3508)<|?at > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.run(RDBMSStoreManager.java:2889)<|?at > > > org.datanucleus.store.rdbms.AbstractSchemaTransaction.execute(AbstractSchemaTransaction.java:119)<|?at > > > org.datanucleus.store.rdbms.RDBMSStoreManager.createSchemaForClasses(RDBMSStoreManager.java:3842)<|?at > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createSchema(DataNucleusApplicationComponents.java:196)<|?at > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createPmfAndSchemaIfRequired(DataNucleusApplicationComponents.java:155)<|?at > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.initialize(DataNucleusApplicationComponents.java:110)<|?at > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.(DataNucleusApplicationComponents.java:103)<|?at > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusPersistenceMechanismInstaller.createDataNucleusApplicationComponentsIfRequired(DataNucleusPersistenceMechanismInstaller.java:134)<|?at > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusPersistenceMechanismInstaller.createObjectStore(DataNucleusPersistenceMechanismInstaller.java:110)<|?at > > > org.apache.isis.core.runtime.system.persistence.PersistenceSessionFactory.createPersistenceSession(PersistenceSessionFactory.java:95)<|?at > > > org.apache.isis.core.runtime.system.session.IsisSessionFactory.openSession(IsisSessionFactory.java:141)<|?at > > > org.apache.isis.core.runtime.system.context.IsisContextThreadLocal.openSessionInstance(IsisContextThreadLocal.java:147)<|?at > > > org.apache.isis.core.runtime.system.context.IsisContext.openSession(IsisContext.java:279)<|?at > > > org.apache.isis.core.runtime.system.IsisSystem.initializeServices(IsisSystem.java:207)<|?at > > > org.apache.isis.core.runtime.system.IsisSystem.init(IsisSystem.java:140)<|?at > > >
Re: datanucleus foreign key name
Hi Andy, Thanks for the feedback. so _OID is to differentiate between class (OID) and element (EID) derived tables. What is an element? Thanks On Mon, Nov 9, 2015 at 5:48 AM, Andy Jeffersonwrote: > >> Just interested to know if there is any way to stop DataNucleus adding > _oid > >> to the end of all its generated foreign keys, this it with > >> @PersistenceCapable( identityType = IdentityType.DATASTORE)? > >> It adds _id_oid to the tail of them all so wondering why? > > > > Don't know why it does it (it is a rather odd name, I agree) but iirc > you > can override it using @Column(name=...) > > FYI : This is documented at > http://www.datanucleus.org/products/accessplatform_4_2/jdo/orm/datastor > e_identifiers.html > > The JPA spec defines what column names should default to. > The JDO spec does not, so DataNucleus provides 4 alternatives (default = > "datanucleus2"), but you also have "jpa", "datanucleus1" and (for those > with very old code) "jpox". > > And if sufficiently interested in there being a JDO spec definition of the > default then kindly participate in Apache JDO issue > https://issues.apache.org/jira/browse/JDO-727 > > > Regards > -- > Andy > DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus) >
Re: views created before tables?
Some frustration on my part and I apologise for any offence caused. On Mon, Nov 9, 2015 at 8:23 AM, Jeroen van der Walwrote: > We're always here to help but please stop blaming Datanucleus and Isis > before thorough root cause analysis. > > On 8 November 2015 at 21:45, Stephen Cameron > wrote: > > > On Mon, Nov 9, 2015 at 12:02 AM, Jeroen van der Wal > > > wrote: > > > > > Have you tried raising the DN logging levels? > > > > > > log4j.logger.DataNucleus.Datastore.Native=DEBUG, Console > > > log4j.logger.DataNucleus.Datastore.Schema=DEBUG, Console > > > > > > Are all the entities the view uses being registered? Eg: are they in > the > > > same package as your AppManifest? > > > > > > > > > Yes same package, I will try this later today and see what I can get > from > > logs. > > > > > > > > On 8 November 2015 at 06:30, Stephen Cameron < > steve.cameron...@gmail.com > > > > > > wrote: > > > > > > > seems to be the case, slightly annoying > > > > > > > > On Sun, Nov 8, 2015 at 3:10 PM, Stephen Cameron < > > > > steve.cameron...@gmail.com> > > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > I am creating some database views via DataNucleus, but am getting > > some > > > > > errors on startup of my webapp (with an clean database so all > tables > > > and > > > > > views get greated). When I look at the new database schema via > MySQL > > > > > workbench I see the views have been created but not the tables, > maybe > > > > this > > > > > is the origin of my errors. > > > > > > > > > > I cannot imagine why DN would do this, create views before creating > > > > tables. > > > > > > > > > > org.datanucleus.exceptions.NucleusDataStoreException: An exception > > was > > > > > thrown while adding/validating class(es) : Query was > > > > > empty|com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: > > Query > > > > was > > > > > empty<|?at > > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > > > > > Method)<|?at > > > > > > > > > > > > > > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)<|?at > > > > > > > > > > > > > > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)<|?at > > > > > > java.lang.reflect.Constructor.newInstance(Constructor.java:422)<|?at > > > > > com.mysql.jdbc.Util.handleNewInstance(Util.java:411)<|?at > > > > > com.mysql.jdbc.Util.getInstance(Util.java:386)<|?at > > > > > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)<|?at > > > > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)<|?at > > > > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)<|?at > > > > > com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)<|?at > > > > > com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)<|?at > > > > > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2619)<|?at > > > > > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2569)<|?at > > > > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:824)<|?at > > > > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:667)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:879)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:830)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.create(AbstractTable.java:546)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.exists(AbstractTable.java:609)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.performViewsValidation(RDBMSStoreManager.java:3508)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.run(RDBMSStoreManager.java:2889)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.AbstractSchemaTransaction.execute(AbstractSchemaTransaction.java:119)<|?at > > > > > > > > > > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager.createSchemaForClasses(RDBMSStoreManager.java:3842)<|?at > > > > > > > > > > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createSchema(DataNucleusApplicationComponents.java:196)<|?at > > > > > > > > > > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createPmfAndSchemaIfRequired(DataNucleusApplicationComponents.java:155)<|?at > > > > > > > > > > > > > > >
Re: datanucleus foreign key name
>> Just interested to know if there is any way to stop DataNucleus adding _oid >> to the end of all its generated foreign keys, this it with >> @PersistenceCapable( identityType = IdentityType.DATASTORE)? >> It adds _id_oid to the tail of them all so wondering why? > > Don't know why it does it (it is a rather odd name, I agree) but iirc you can override it using @Column(name=...) FYI : This is documented at http://www.datanucleus.org/products/accessplatform_4_2/jdo/orm/datastor e_identifiers.html The JPA spec defines what column names should default to. The JDO spec does not, so DataNucleus provides 4 alternatives (default = "datanucleus2"), but you also have "jpa", "datanucleus1" and (for those with very old code) "jpox". And if sufficiently interested in there being a JDO spec definition of the default then kindly participate in Apache JDO issue https://issues.apache.org/jira/browse/JDO-727 Regards -- Andy DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus)
Re: views created before tables?
Thanks, I will create a test case and debug it, maybe the issue is I don't have a explicit persistence definition in Isis (do I?) so maybe there is something wrong in Isis. On Mon, Nov 9, 2015 at 5:52 AM, Andy Jeffersonwrote: > > I am creating some database views via DataNucleus, but am getting > some > > errors on startup of my webapp (with an clean database so all tables > and > > views get greated). When I look at the new database schema via MySQL > > workbench I see the views have been created but not the tables, maybe > this > > is the origin of my errors. > > I cannot imagine why DN would do this, create views before creating > tables. > > I can't either, but then I know for a fact that it creates tables BEFORE > views, and simple inspection of the code that your stack trace refers to > points to > > https://github.com/datanucleus/datanucleus-rdbms/blob/4.1/src/main/java/org/datanucleus/store/rdbms/RDBMSStoreMa > nager.java#L2874 > > so you must have something wrong with your persistence definition (or > something missing). > > > > > Regards > -- > Andy > DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus) >
Re: views created before tables?
We're always here to help but please stop blaming Datanucleus and Isis before thorough root cause analysis. On 8 November 2015 at 21:45, Stephen Cameronwrote: > On Mon, Nov 9, 2015 at 12:02 AM, Jeroen van der Wal > wrote: > > > Have you tried raising the DN logging levels? > > > > log4j.logger.DataNucleus.Datastore.Native=DEBUG, Console > > log4j.logger.DataNucleus.Datastore.Schema=DEBUG, Console > > > > Are all the entities the view uses being registered? Eg: are they in the > > same package as your AppManifest? > > > > > > Yes same package, I will try this later today and see what I can get from > logs. > > > > > On 8 November 2015 at 06:30, Stephen Cameron > > > wrote: > > > > > seems to be the case, slightly annoying > > > > > > On Sun, Nov 8, 2015 at 3:10 PM, Stephen Cameron < > > > steve.cameron...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > I am creating some database views via DataNucleus, but am getting > some > > > > errors on startup of my webapp (with an clean database so all tables > > and > > > > views get greated). When I look at the new database schema via MySQL > > > > workbench I see the views have been created but not the tables, maybe > > > this > > > > is the origin of my errors. > > > > > > > > I cannot imagine why DN would do this, create views before creating > > > tables. > > > > > > > > org.datanucleus.exceptions.NucleusDataStoreException: An exception > was > > > > thrown while adding/validating class(es) : Query was > > > > empty|com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: > Query > > > was > > > > empty<|?at > > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > > > > Method)<|?at > > > > > > > > > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)<|?at > > > > > > > > > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)<|?at > > > > java.lang.reflect.Constructor.newInstance(Constructor.java:422)<|?at > > > > com.mysql.jdbc.Util.handleNewInstance(Util.java:411)<|?at > > > > com.mysql.jdbc.Util.getInstance(Util.java:386)<|?at > > > > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)<|?at > > > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)<|?at > > > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)<|?at > > > > com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)<|?at > > > > com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)<|?at > > > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2619)<|?at > > > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2569)<|?at > > > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:824)<|?at > > > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:667)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:879)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:830)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.create(AbstractTable.java:546)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.exists(AbstractTable.java:609)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.performViewsValidation(RDBMSStoreManager.java:3508)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.run(RDBMSStoreManager.java:2889)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.AbstractSchemaTransaction.execute(AbstractSchemaTransaction.java:119)<|?at > > > > > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager.createSchemaForClasses(RDBMSStoreManager.java:3842)<|?at > > > > > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createSchema(DataNucleusApplicationComponents.java:196)<|?at > > > > > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createPmfAndSchemaIfRequired(DataNucleusApplicationComponents.java:155)<|?at > > > > > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.initialize(DataNucleusApplicationComponents.java:110)<|?at > > > > > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.(DataNucleusApplicationComponents.java:103)<|?at > > > > > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusPersistenceMechanismInstaller.createDataNucleusApplicationComponentsIfRequired(DataNucleusPersistenceMechanismInstaller.java:134)<|?at > > > > > > > > > >
Re: views created before tables?
On Mon, Nov 9, 2015 at 12:02 AM, Jeroen van der Walwrote: > Have you tried raising the DN logging levels? > > log4j.logger.DataNucleus.Datastore.Native=DEBUG, Console > log4j.logger.DataNucleus.Datastore.Schema=DEBUG, Console > > Are all the entities the view uses being registered? Eg: are they in the > same package as your AppManifest? > > > Yes same package, I will try this later today and see what I can get from logs. > > On 8 November 2015 at 06:30, Stephen Cameron > wrote: > > > seems to be the case, slightly annoying > > > > On Sun, Nov 8, 2015 at 3:10 PM, Stephen Cameron < > > steve.cameron...@gmail.com> > > wrote: > > > > > Hi, > > > > > > I am creating some database views via DataNucleus, but am getting some > > > errors on startup of my webapp (with an clean database so all tables > and > > > views get greated). When I look at the new database schema via MySQL > > > workbench I see the views have been created but not the tables, maybe > > this > > > is the origin of my errors. > > > > > > I cannot imagine why DN would do this, create views before creating > > tables. > > > > > > org.datanucleus.exceptions.NucleusDataStoreException: An exception was > > > thrown while adding/validating class(es) : Query was > > > empty|com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Query > > was > > > empty<|?at > sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > > > Method)<|?at > > > > > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)<|?at > > > > > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)<|?at > > > java.lang.reflect.Constructor.newInstance(Constructor.java:422)<|?at > > > com.mysql.jdbc.Util.handleNewInstance(Util.java:411)<|?at > > > com.mysql.jdbc.Util.getInstance(Util.java:386)<|?at > > > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)<|?at > > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)<|?at > > > com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)<|?at > > > com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)<|?at > > > com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)<|?at > > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2619)<|?at > > > com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2569)<|?at > > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:824)<|?at > > > com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:667)<|?at > > > > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > > > > org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:246)<|?at > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:879)<|?at > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:830)<|?at > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.create(AbstractTable.java:546)<|?at > > > > > > org.datanucleus.store.rdbms.table.AbstractTable.exists(AbstractTable.java:609)<|?at > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.performViewsValidation(RDBMSStoreManager.java:3508)<|?at > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.run(RDBMSStoreManager.java:2889)<|?at > > > > > > org.datanucleus.store.rdbms.AbstractSchemaTransaction.execute(AbstractSchemaTransaction.java:119)<|?at > > > > > > org.datanucleus.store.rdbms.RDBMSStoreManager.createSchemaForClasses(RDBMSStoreManager.java:3842)<|?at > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createSchema(DataNucleusApplicationComponents.java:196)<|?at > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createPmfAndSchemaIfRequired(DataNucleusApplicationComponents.java:155)<|?at > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.initialize(DataNucleusApplicationComponents.java:110)<|?at > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.(DataNucleusApplicationComponents.java:103)<|?at > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusPersistenceMechanismInstaller.createDataNucleusApplicationComponentsIfRequired(DataNucleusPersistenceMechanismInstaller.java:134)<|?at > > > > > > org.apache.isis.objectstore.jdo.datanucleus.DataNucleusPersistenceMechanismInstaller.createObjectStore(DataNucleusPersistenceMechanismInstaller.java:110)<|?at > > > > > > org.apache.isis.core.runtime.system.persistence.PersistenceSessionFactory.createPersistenceSession(PersistenceSessionFactory.java:95)<|?at > > > > > > org.apache.isis.core.runtime.system.session.IsisSessionFactory.openSession(IsisSessionFactory.java:141)<|?at > > > > > >