In my opinion, when I used these tutorials, the Extended Pet Clinic one in 
github is much more explicit and detailed, probably you might want to choose 
one to facilitate keeping it up to date and smooth.

By the way, I loved the swagger integration since then!

-----Original Message-----
From: Jeroen van der Wal [mailto:[email protected]]
Sent: Thursday, March 10, 2016 1:53 AM
To: users
Subject: Re: Problem in petclinic tutorial // schema name incorrect

We've had a similar issue a while ago when mixing different schemas within the 
same dom project. I suggest for the sake of a smooth tutorial to remove all 
schema directives.

Separately, the tutorial probably uses an old version of Isis and I know there 
have been some improvements in this field.



On 9 March 2016 at 20:37, Angel Manuel Barrera Lugo < 
[email protected]> wrote:

> postgresql is case sensitive
>
>
> 1.- do everything in the petclinic-extended until, finished the
> changes made in step5
>
> 2.- Install postgreSQL and create the scheme "petclinic"
> 3.- Run the schema tool (eclipse), it shows:
> mar 09, 2016 1:27:01 PM org.datanucleus.metadata.MetaDataManager
> loadClasses
> GRAVE: �La clase domainapp.dom.modules.petclinic.QPet is not in the
> CLASSPATH!. Por favor compruebe la especificaci�n y el CLASSPATH.
>
> org.datanucleus.exceptions.ClassNotResolvedException: �La clase
> domainapp.dom.modules.petclinic.QPet no esta en el CLASSPATH!. Por
> favor compruebe la especificaci�n y el CLASSPATH.
>
>
> mar 09, 2016 1:27:01 PM org.datanucleus.store.schema.SchemaTool main
> INFORMACIÓN: SchemaTool ha terminado con exito SchemaTool ha terminado
> con exito
>
>
> 4.- after that i run the petclinic as Mavel Build... with goals "clean
> install"
> they show me this:
>
> Caused by: org.hsqldb.HsqlException: nombre de esquema incorrecto:
> PETCLINIC
>     at org.hsqldb.error.Error.error(Unknown Source)
>     at org.hsqldb.error.Error.error(Unknown Source)
>     at org.hsqldb.SchemaManager.getSchemaHsqlName(Unknown Source)
>     at org.hsqldb.Session.getSchemaHsqlName(Unknown Source)
>     at org.hsqldb.StatementSchema.setOrCheckObjectName(Unknown Source)
>     at org.hsqldb.StatementSchema.getResult(Unknown Source)
>     at org.hsqldb.StatementSchema.execute(Unknown Source)
>     at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
>     at org.hsqldb.Session.executeDirectStatement(Unknown Source)
>     at org.hsqldb.Session.execute(Unknown Source)
>     ... 27 more
>
> 13:33:32,608  [Schema               Thread-0   DEBUG]  Hay un error en la
> creaci�n de los elementos del esquema - restaurando
> 13:33:32,608  [Schema               Thread-0   DEBUG]  Rolling back
> transaccion del esquema
> "org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGua
> rdConnectionWrapper@273977c1
> "
> 13:33:32,608  [Schema               Thread-0   DEBUG]  Cerrando la
> conneccion de la transaccion del esquema
> "org.datanucleus.store.rdbms.datasource.dbcp.PoolingDataSource$PoolGua
> rdConnectionWrapper@273977c1
> "
> Una excepcion estaba tirada durante la addicion/validacion de algunas
> class(es) : nombre de esquema incorrecto: PETCLINIC in statement
> [CREATE TABLE petclinic."Pet"
> (
>     "id" BIGINT GENERATED BY DEFAULT AS IDENTITY,
>     "name" NVARCHAR(40) NOT NULL,
>     "version" BIGINT NOT NULL,
>     CONSTRAINT "Pet_PK" PRIMARY KEY ("id") )]
> java.sql.SQLException: nombre de esquema incorrecto: PETCLINIC in
> statement [CREATE TABLE petclinic."Pet"
> (
>     "id" BIGINT GENERATED BY DEFAULT AS IDENTITY,
>     "name" NVARCHAR(40) NOT NULL,
>     "version" BIGINT NOT NULL,
>     CONSTRAINT "Pet_PK" PRIMARY KEY ("id") )]
>     at org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
>     at org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
>     at org.hsqldb.jdbc.JDBCStatement.fetchResult(Unknown Source)
>     at org.hsqldb.jdbc.JDBCStatement.execute(Unknown Source)
>     at
> org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
>     at
> org.datanucleus.store.rdbms.datasource.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
>     at
> org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:760)
>     at
> org.datanucleus.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:711)
>     at
> org.datanucleus.store.rdbms.table.AbstractTable.create(AbstractTable.java:425)
>     at
> org.datanucleus.store.rdbms.table.AbstractTable.exists(AbstractTable.java:488)
>     at
> org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.performTablesValidation(RDBMSStoreManager.java:3380)
>     at
> org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.addClassTablesAndValidate(RDBMSStoreManager.java:3190)
>     at
> org.datanucleus.store.rdbms.RDBMSStoreManager$ClassAdder.run(RDBMSStoreManager.java:2841)
>     at
> org.datanucleus.store.rdbms.AbstractSchemaTransaction.execute(AbstractSchemaTransaction.java:122)
>     at
> org.datanucleus.store.rdbms.RDBMSStoreManager.createSchema(RDBMSStoreManager.java:4051)
>     at
> org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.createSchema(DataNucleusApplicationComponents.java:127)
>     at
> org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.init(DataNucleusApplicationComponents.java:111)
>     at
> org.apache.isis.objectstore.jdo.datanucleus.DataNucleusApplicationComponents.<init>(DataNucleusApplicationComponents.java:97)
>     at
> org.apache.isis.objectstore.jdo.datanucleus.DataNucleusPersistenceMechanismInstaller.createDataNucleusApplicationComponentsIfRequired(DataNucleusPersistenceMechanismInstaller.java:112)
>     at
> org.apache.isis.objectstore.jdo.datanucleus.DataNucleusPersistenceMechanismInstaller.createObjectStore(DataNucleusPersistenceMechanismInstaller.java:89)
>     at
> org.apache.isis.core.runtime.system.persistence.PersistenceSessionFactory.createPersistenceSession(PersistenceSessionFactory.java:94)
>     at
> org.apache.isis.core.runtime.system.session.IsisSessionFactoryDefault.openSession(IsisSessionFactoryDefault.java:217)
>     at
> org.apache.isis.core.runtime.system.context.IsisContextStatic.openSessionInstance(IsisContextStatic.java:70)
>     at
> org.apache.isis.core.runtime.system.context.IsisContext.openSession(IsisContext.java:275)
>     at
> org.apache.isis.core.runtime.system.IsisSystemFixturesHookAbstract.shutdownServices(IsisSystemFixturesHookAbstract.java:183)
>     at
> org.apache.isis.core.runtime.system.IsisSystemFixturesHookAbstract.shutdown(IsisSystemFixturesHookAbstract.java:172)
>     at
> org.apache.isis.core.integtestsupport.IsisSystemForTest.shutdown(IsisSystemForTest.java:429)
>     at
> org.apache.isis.core.integtestsupport.IsisSystemForTest.access$100(IsisSystemForTest.java:67)
>     at
> org.apache.isis.core.integtestsupport.IsisSystemForTest$Builder$1.run(
> IsisSystemForTest.java:265) Caused by: org.hsqldb.HsqlException:
> nombre de esquema incorrecto:
> PETCLINIC
>     at org.hsqldb.error.Error.error(Unknown Source)
>     at org.hsqldb.error.Error.error(Unknown Source)
>     at org.hsqldb.SchemaManager.getSchemaHsqlName(Unknown Source)
>     at org.hsqldb.Session.getSchemaHsqlName(Unknown Source)
>     at org.hsqldb.StatementSchema.setOrCheckObjectName(Unknown Source)
>     at org.hsqldb.StatementSchema.getResult(Unknown Source)
>     at org.hsqldb.StatementSchema.execute(Unknown Source)
>     at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
>     at org.hsqldb.Session.executeDirectStatement(Unknown Source)
>     at org.hsqldb.Session.execute(Unknown Source)
>     ... 27 more
>
> org.datanucleus.exceptions.NucleusDataStoreException: Una excepcion
> estaba tirada durante la addicion/validacion de algunas class(es) :
> nombre de esquema incorrecto: PETCLINIC in statement [CREATE TABLE 
> petclinic."Pet"
> (
>     "id" BIGINT GENERATED BY DEFAULT AS IDENTITY,
>     "name" NVARCHAR(40) NOT NULL,
>     "version" BIGINT NOT NULL,
>     CONSTRAINT "Pet_PK" PRIMARY KEY ("id") )]
>
>
>
> ________________________________
> De: Dan Haywood <[email protected]>
> Enviado: miércoles, 9 de marzo de 2016 01:15 p. m.
> Para: Angel Manuel Barrera Lugo
> Cc: users
> Asunto: Re: Problem in petclinic tutorial // schema name incorrect
>
>
> I'm trying to remember, is postgresql case sensitive?
>
> There's some code in Isis that applies some heuristics for this; is
> also puddings to use the raw underlying datanucleus properties to
> influence things.
>
> Could you spell out exactly what you did to create the error so I can
> try to replicate?
>
> Thx, Dan
>
> On 9 Mar 2016 19:08, "Angel Manuel Barrera Lugo" <
> [email protected]<mailto:[email protected]>> wrote:
>
> Well finally i have the schema (postgresSQL) and everything but still
> have this error:
>
> Caused by: org.hsqldb.HsqlException: nombre de esquema incorrecto:
> PETCLINIC
>     at org.hsqldb.error.Error.error(Unknown Source)
>     at org.hsqldb.error.Error.error(Unknown Source)
>     at org.hsqldb.SchemaManager.getSchemaHsqlName(Unknown Source)
>     at org.hsqldb.Session.getSchemaHsqlName(Unknown Source)
>     at org.hsqldb.StatementSchema.setOrCheckObjectName(Unknown Source)
>     at org.hsqldb.StatementSchema.getResult(Unknown Source)
>     at org.hsqldb.StatementSchema.execute(Unknown Source)
>     at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
>     at org.hsqldb.Session.executeDirectStatement(Unknown Source)
>     at org.hsqldb.Session.execute(Unknown Source)
>     ... 64 more
>
> Caused by: java.sql.SQLException: nombre de esquema incorrecto:
> PETCLINIC in statement [CREATE TABLE petclinic."Pet"
> (
>     "id" BIGINT GENERATED BY DEFAULT AS IDENTITY,
>     "name" NVARCHAR(40) NOT NULL,
>     "version" BIGINT NOT NULL,
>     CONSTRAINT "Pet_PK" PRIMARY KEY ("id") )]
>


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Reply via email to