openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick" <michael.d.d...@gmail.com>
Subject Re: [continuum] BUILD FAILURE: OpenJPA JPA JDBC
Date Wed, 09 May 2007 23:13:16 GMT
This should be fixed with revision 536706.  I deleted the testcase and the
entities (probably overkill).

-mike

On 5/9/07, Continuum@vmbuild.apache.org <
open-jpa-commits@incubator.apache.org> wrote:
>
> Online report :
> http://vmbuild.apache.org/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/87/buildId/140859
> Build statistics:
>   State: Failed
>   Previous State: Ok
>   Started at: Wed, 9 May 2007 16:02:44 -0700
>   Finished at: Wed, 9 May 2007 16:09:21 -0700
>   Total time: 6m 36s
>   Build Trigger: Schedule
>   Exit code: 1
>   Building machine hostname: vmbuild.apache.org
>   Operating system : Linux(unknown)
>   Java version : 1.5.0_06(Sun Microsystems Inc.)
>
> Changes
>          mprudhom          OPENJPA-194 Changed openjpa-all-VERSION.jar to
> be just openjpa-VERSION.jar, and changes openjpa-project-VERSION.zip to be
> apache-openjpa-VERSION.zip
>              /incubator/openjpa/trunk/openjpa-all/pom.xml
>             /incubator/openjpa/trunk/openjpa-examples/pom.xml
>             /incubator/openjpa/trunk/openjpa-integration/examples/pom.xml
>             /incubator/openjpa/trunk/openjpa-integration/pom.xml
>             /incubator/openjpa/trunk/openjpa-jdbc/pom.xml
>             /incubator/openjpa/trunk/openjpa-jdbc-5/pom.xml
>             /incubator/openjpa/trunk/openjpa-kernel/pom.xml
>             /incubator/openjpa/trunk/openjpa-kernel-5/pom.xml
>             /incubator/openjpa/trunk/openjpa-lib/pom.xml
>             /incubator/openjpa/trunk/openjpa-persistence/pom.xml
>             /incubator/openjpa/trunk/openjpa-persistence-jdbc/pom.xml
>             /incubator/openjpa/trunk/openjpa-project/assembly.xml
>             /incubator/openjpa/trunk/openjpa-project/pom.xml
>             /incubator/openjpa/trunk/openjpa-xmlstore/pom.xml
>             /incubator/openjpa/trunk/pom.xml
>
>
> ****************************************************************************
> Output:
>
> ****************************************************************************
> [INFO] Scanning for projects...
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Building OpenJPA JPA JDBC
> [INFO]    task-segment: [clean, install]
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] Deleting directory /x1/continuum/working-directory/87/target
> [INFO] Deleting directory
> /x1/continuum/working-directory/87/target/classes
> [INFO] Deleting directory
> /x1/continuum/working-directory/87/target/test-classes
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] snapshot
> org.apache.openjpa:openjpa-jdbc-5:0.9.8-incubating-SNAPSHOT: checking for
> updates from central
> [INFO] snapshot
> org.apache.openjpa:openjpa-persistence:0.9.8-incubating-SNAPSHOT: checking
> for updates from central
> [INFO] [compiler:compile]
> Compiling 43 source files to
> /x1/continuum/working-directory/87/target/classes
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> Compiling 150 source files to
> /x1/continuum/working-directory/87/target/test-classes
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> 2724  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.TestMultipleSameTypedEmbeddedWithEagerRelations"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.TestMultipleSameTypedEmbeddedWithEagerRelations"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.TestMultipleSameTypedEmbeddedWithEagerRelations".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 2786  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.test.SQLListenerTestCase" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.test.SQLListenerTestCase" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.test.SQLListenerTestCase". This can happen
> if the directory containing your metadata is not in your CLASSPATH, or if
> your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 3530  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.conf.TestAutoDetachProperty" has no metadata; enhancing
> as persistence aware. If you intended for "class
> org.apache.openjpa.conf.TestAutoDetachProperty" to be persistence-capable,
> then this means that OpenJPA could not find any metadata for "class
> org.apache.openjpa.conf.TestAutoDetachProperty". This can happen if the
> directory containing your metadata is not in your CLASSPATH, or if your
> metadata files are not named properly. See the documentation on metadata
> placement for more information.
> 3573  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.conf.TestBadAutoDetachProperty" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.conf.TestBadAutoDetachProperty" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.conf.TestBadAutoDetachProperty".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 3619  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.detachment.TestGetReferenceAndImplicitDetachment"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.detachment.TestGetReferenceAndImplicitDetachment"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.detachment.TestGetReferenceAndImplicitDetachment".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 4300  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.ManyOneCompoundIdOwnerId" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.ManyOneCompoundIdOwnerId" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.ManyOneCompoundIdOwnerId". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 4518  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.TestManyOneAsId" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.TestManyOneAsId" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.TestManyOneAsId". This can happen
> if the directory containing your metadata is not in your CLASSPATH, or if
> your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 4640  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.detachment.TestDetachmentOneMany" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.detachment.TestDetachmentOneMany" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.detachment.TestDetachmentOneMany". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 4834  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.inheritance.TestMultipleMappedSuperclassHierarchy"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.inheritance.TestMultipleMappedSuperclassHierarchy"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.inheritance.TestMultipleMappedSuperclassHierarchy".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 4859  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.inheritance.TestSharedUnqualifiedClassNames"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.inheritance.TestSharedUnqualifiedClassNames"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.inheritance.TestSharedUnqualifiedClassNames".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 5508  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.identity.TestGenerationType" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.identity.TestGenerationType" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.identity.TestGenerationType". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 5548  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.query.TestSubQuery" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.query.TestSubQuery" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.persistence.query.TestSubQuery".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 6217  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.jdbc.TestIsolationLevelOverride" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.jdbc.TestIsolationLevelOverride" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.jdbc.TestIsolationLevelOverride". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 6266  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.TestLRS" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.TestLRS" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.persistence.relations.TestLRS".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 6947  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.models.company.fetchlazy.TestLazyCompanyModel"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.models.company.fetchlazy.TestLazyCompanyModel"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.models.company.fetchlazy.TestLazyCompanyModel".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 6957  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.identity.TestFloatingPointIds" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.identity.TestFloatingPointIds" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.identity.TestFloatingPointIds". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 7666  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.kernel.TestQueryCompilationCache" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.kernel.TestQueryCompilationCache" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.kernel.TestQueryCompilationCache".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 8064  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.inheritance.TestSharedMappedSuperclassIdValue"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.inheritance.TestSharedMappedSuperclassIdValue"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.inheritance.TestSharedMappedSuperclassIdValue".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 8316  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.datacache.TestDataCacheOptimisticLockRecovery"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.datacache.TestDataCacheOptimisticLockRecovery"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.datacache.TestDataCacheOptimisticLockRecovery".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 8529  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.xml.TestSimpleXmlEntity" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.xml.TestSimpleXmlEntity" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.persistence.xml.TestSimpleXmlEntity".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 8552  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.test.SQLListenerTestCase$Listener" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.test.SQLListenerTestCase$Listener" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.test.SQLListenerTestCase$Listener". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 8568  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.jdbc.meta.TestMappingToolAutoDelete" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.jdbc.meta.TestMappingToolAutoDelete" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.jdbc.meta.TestMappingToolAutoDelete".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 8769  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.jdbc.kernel.TestNoForeignKeyViolation" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.jdbc.kernel.TestNoForeignKeyViolation" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.jdbc.kernel.TestNoForeignKeyViolation". This can happen
> if the directory containing your metadata is not in your CLASSPATH, or if
> your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 8917  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.query.CustomerEntity$CreditRating" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.query.CustomerEntity$CreditRating" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.query.CustomerEntity$CreditRating". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 9435  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.test.SingleEMTestCase" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.test.SingleEMTestCase" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.persistence.test.SingleEMTestCase".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 9493  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.query.TestResultSetMapping" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.query.TestResultSetMapping" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.query.TestResultSetMapping". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 9667  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.callbacks.ExceptionsFromCallbacksEntity$CallbackTestException"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.callbacks.ExceptionsFromCallbacksEntity$CallbackTestException"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.callbacks.ExceptionsFromCallbacksEntity$CallbackTestException".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 9677  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.query.TestQueryExcludingSubclasses" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.query.TestQueryExcludingSubclasses" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.query.TestQueryExcludingSubclasses". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 9804  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.inheritance.TestFindAbstractClass" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.inheritance.TestFindAbstractClass" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.inheritance.TestFindAbstractClass". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 10068  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.models.company.joined.TestJoinedCompanyModel"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.models.company.joined.TestJoinedCompanyModel"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.models.company.joined.TestJoinedCompanyModel".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 10075  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.models.company.idclass.TestIdClassCompanyModel"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.models.company.idclass.TestIdClassCompanyModel"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.models.company.idclass.TestIdClassCompanyModel".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 10218  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.callbacks.TestExceptionsFromCallbacks" has
> no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.callbacks.TestExceptionsFromCallbacks" to
> be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.callbacks.TestExceptionsFromCallbacks".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 10273  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.simple.TestEntityManagerClear" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.simple.TestEntityManagerClear" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.simple.TestEntityManagerClear". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 10297  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.detachment.TestAttachWithNoChanges" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.detachment.TestAttachWithNoChanges" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.detachment.TestAttachWithNoChanges". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 10342  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.TestCascadingOneManyWithForeignKey"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.TestCascadingOneManyWithForeignKey"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.TestCascadingOneManyWithForeignKey".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 10525  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.models.company.CompanyModelTest" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.models.company.CompanyModelTest" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.models.company.CompanyModelTest". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 10663  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.models.company.CompanyModelTest$1" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.models.company.CompanyModelTest$1" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.models.company.CompanyModelTest$1". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 11469  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.query.TestInMemoryQueryMatchEscapes" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.query.TestInMemoryQueryMatchEscapes" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.query.TestInMemoryQueryMatchEscapes". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 11500  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.xml.TestXmlOverrideEntity" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.xml.TestXmlOverrideEntity" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.xml.TestXmlOverrideEntity". This can happen
> if the directory containing your metadata is not in your CLASSPATH, or if
> your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 11920  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.identity.TestSQLDateId" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.identity.TestSQLDateId" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.persistence.identity.TestSQLDateId".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 12168  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.simple.TestCaseInsensitiveKeywordsInJPQL"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.simple.TestCaseInsensitiveKeywordsInJPQL"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.simple.TestCaseInsensitiveKeywordsInJPQL".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 12394  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.simple.TestEntityManagerMethodsThrowAfterClose"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.simple.TestEntityManagerMethodsThrowAfterClose"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.simple.TestEntityManagerMethodsThrowAfterClose".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 12521  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.query.TestQueryIdOfRelationDoesNotJoin" has
> no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.query.TestQueryIdOfRelationDoesNotJoin" to
> be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.query.TestQueryIdOfRelationDoesNotJoin".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 12577  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.jdbc.TestSelectForUpdateOverride" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.jdbc.TestSelectForUpdateOverride" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.jdbc.TestSelectForUpdateOverride". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 14550  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.datacache.TestArrayFieldsInDataCache" has
> no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.datacache.TestArrayFieldsInDataCache" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.datacache.TestArrayFieldsInDataCache". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 14867  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.TestEagerBidiSQL" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.TestEagerBidiSQL" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.TestEagerBidiSQL". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 15214  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.test.PersistenceTestCase" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.test.PersistenceTestCase" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.test.PersistenceTestCase". This can happen
> if the directory containing your metadata is not in your CLASSPATH, or if
> your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 15275  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.simple.TestTableNamesDefaultToEntityNames"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.simple.TestTableNamesDefaultToEntityNames"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.simple.TestTableNamesDefaultToEntityNames".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 15629  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.TestTargetedIFaceRelations" has
> no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.TestTargetedIFaceRelations" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.TestTargetedIFaceRelations". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 15807  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.query.TestAbstractSchemaName" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.query.TestAbstractSchemaName" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.query.TestAbstractSchemaName". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 15834  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.datacache.TestBulkJPQLAndDataCache" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.datacache.TestBulkJPQLAndDataCache" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.datacache.TestBulkJPQLAndDataCache". This
> can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 15876  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.ManyOneCompoundIdOwnerId$Tokenizer"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.ManyOneCompoundIdOwnerId$Tokenizer"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.ManyOneCompoundIdOwnerId$Tokenizer".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 16042  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.simple.TestPersistence" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.simple.TestPersistence" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.persistence.simple.TestPersistence".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 16254  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.relations.TestIdOrderedOneMany" has no
> metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.relations.TestIdOrderedOneMany" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.relations.TestIdOrderedOneMany". This can
> happen if the directory containing your metadata is not in your CLASSPATH,
> or if your metadata files are not named properly. See the documentation on
> metadata placement for more information.
> 16346  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.test.SingleEMFTestCase" has no metadata;
> enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.test.SingleEMFTestCase" to be
> persistence-capable, then this means that OpenJPA could not find any
> metadata for "class org.apache.openjpa.persistence.test.SingleEMFTestCase".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> 16483  test  WARN   [main] openjpa.Enhance - Type "class
> org.apache.openjpa.persistence.models.company.basic.TestBasicCompanyModel"
> has no metadata; enhancing as persistence aware. If you intended for "class
> org.apache.openjpa.persistence.models.company.basic.TestBasicCompanyModel"
> to be persistence-capable, then this means that OpenJPA could not find any
> metadata for "class
> org.apache.openjpa.persistence.models.company.basic.TestBasicCompanyModel".
> This can happen if the directory containing your metadata is not in your
> CLASSPATH, or if your metadata files are not named properly. See the
> documentation on metadata placement for more information.
> [INFO] Executed tasks
> [INFO] [surefire:test]
> [INFO] Surefire report directory:
> /x1/continuum/working-directory/87/target/surefire-reports
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.openjpa.conf.TestAutoDetachProperty
> 90  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 279  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to
> the database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 6961  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 4  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 6  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 12  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 14  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.542 sec
> Running org.apache.openjpa.persistence.relations.TestEagerBidiSQL
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 14  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 7  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 9  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 9  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.44 sec
> Running org.apache.openjpa.persistence.query.TestResultSetMapping
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 7  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.582 sec
> Running org.apache.openjpa.persistence.query.TestAbstractSchemaName
> 2  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 7  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.511 sec
> Running
> org.apache.openjpa.persistence.models.company.joined.TestJoinedCompanyModel
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 47161  test  WARN   [main] openjpa.Runtime - Detected possible orphaned
> reference to deleted object "
> org.apache.openjpa.persistence.models.company.joined.Address-1178751820198"
> in "
> org.apache.openjpa.persistence.models.company.joined.Person.homeAddress".
> 47171  test  WARN   [main] openjpa.Runtime - Detected possible orphaned
> reference to deleted object "
> org.apache.openjpa.persistence.models.company.joined.Company-1178751820202"
> in "org.apache.openjpa.persistence.models.company.joined.Employee.company
> ".
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 47.373 sec
> Running
> org.apache.openjpa.persistence.relations.TestCascadingOneManyWithForeignKey
> 4  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 6  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 10  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 6  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.561 sec
> Running
> org.apache.openjpa.persistence.detachment.TestGetReferenceAndImplicitDetachment
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 9  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.887 sec
> Running org.apache.openjpa.persistence.relations.TestManyOneAsId
> 9  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 10  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to
> the database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 14  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 11  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 12  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 2  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 6  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 0  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 10  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 6  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 10  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 64.372sec
> Running org.apache.openjpa.persistence.detachment.TestDetachmentOneMany
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.533 sec
> Running
> org.apache.openjpa.persistence.inheritance.TestSharedMappedSuperclassIdValue
> 4  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 5  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 7  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.676 sec
> Running org.apache.openjpa.persistence.inheritance.TestFindAbstractClass
> 2  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 6  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.481 sec
> Running
> org.apache.openjpa.persistence.models.company.fetchlazy.TestLazyCompanyModel
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.754 sec
> Running org.apache.openjpa.persistence.identity.TestSQLDateId
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 8  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.626 sec
> Running
> org.apache.openjpa.persistence.models.company.basic.TestBasicCompanyModel
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.209 sec
> Running
> org.apache.openjpa.persistence.simple.TestCaseInsensitiveKeywordsInJPQL
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 32  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 347  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.115 sec
> Running
> org.apache.openjpa.persistence.simple.TestTableNamesDefaultToEntityNames
> 0  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 18  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.14 sec
> Running org.apache.openjpa.kernel.TestQueryCompilationCache
> 5  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 6  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 8  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.112 sec
> Running org.apache.openjpa.persistence.simple.TestEntityManagerClear
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 20  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 58  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.128 sec
> Running org.apache.openjpa.persistence.query.TestSubQuery
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.84 sec
> <<< FAILURE!
> testQuery(org.apache.openjpa.persistence.query.TestSubQuery)  Time
> elapsed: 0.829 sec  <<< ERROR!
> <0.0.0 fatal store error> org.apache.openjpa.persistence.RollbackException:
> The transaction cannot be committed, because it was already marked for
> rollback only.  The transaction will be rolled back instead. The cause of
> the rollback-only status is reported in the embedded stack.
>         at org.apache.openjpa.persistence.EntityManagerImpl.commit(
> EntityManagerImpl.java:420)
>         at org.apache.openjpa.persistence.query.TestSubQuery.testQuery(
> TestSubQuery.java:85)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at junit.framework.TestCase.runTest(TestCase.java:154)
>         at junit.framework.TestCase.runBare(TestCase.java:127)
>         at junit.framework.TestResult$1.protect(TestResult.java:106)
>         at junit.framework.TestResult.runProtected(TestResult.java:124)
>         at junit.framework.TestResult.run(TestResult.java:109)
>         at junit.framework.TestCase.run(TestCase.java:118)
>         at junit.framework.TestSuite.runTest(TestSuite.java:208)
>         at junit.framework.TestSuite.run(TestSuite.java:203)
>         at sun.reflect.GeneratedMethodAccessor178.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.apache.maven.surefire.junit.JUnitTestSet.execute(
> JUnitTestSet.java:210)
>         at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(
> AbstractDirectoryTestSuite.java:135)
>         at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(
> AbstractDirectoryTestSuite.java:122)
>         at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
> SurefireBooter.java:225)
>         at org.apache.maven.surefire.booter.SurefireBooter.main(
> SurefireBooter.java:747)
> Caused by: <0.0.0 fatal general error>
> org.apache.openjpa.persistence.PersistenceException: The transaction
> cannot be committed, because it was already marked for rollback only.  The
> transaction will be rolled back instead. The cause of the rollback-only
> status is reported in the embedded stack.
>         at org.apache.openjpa.kernel.LocalManagedRuntime.commit(
> LocalManagedRuntime.java:88)
>         at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java
> :1319)
>         at org.apache.openjpa.kernel.DelegatingBroker.commit(
> DelegatingBroker.java:866)
>         at org.apache.openjpa.persistence.EntityManagerImpl.commit(
> EntityManagerImpl.java:409)
>         ... 26 more
> Caused by: <0.0.0 nonfatal general error>
> org.apache.openjpa.persistence.PersistenceException: Syntax error:
> Encountered "WHERE" at line 1, column 117. {UPDATE ORDERTB SET amount =
> (CAST(amount AS DOUBLE) + CAST(? AS DOUBLE)) WHERE oid IN (SELECT DISTINCT
> t2.oid FROM  WHERE (NOT (t2.oid IN (SELECT t1.oid FROM  WHERE t0.cid =
> t1.customer_cid))))} [code=20000, state=42X01]
> FailedObject: org.apache.openjpa.jdbc.kernel.exps.ExpContext@1d764fe
>         at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(
> DBDictionary.java:3784)
>         at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(
> SQLExceptions.java:97)
>         at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(
> SQLExceptions.java:67)
>         at
> org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeBulkOperation(
> JDBCStoreQuery.java:508)
>         at org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeUpdate(
> JDBCStoreQuery.java:430)
>         at
> org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.executeUpdate
> (ExpressionStoreQuery.java:690)
>         at org.apache.openjpa.kernel.QueryImpl.update(QueryImpl.java:1036)
>         at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:800)
>         at org.apache.openjpa.kernel.QueryImpl.updateAll(QueryImpl.java
> :875)
>         at org.apache.openjpa.kernel.QueryImpl.updateAll(QueryImpl.java
> :871)
>         at org.apache.openjpa.kernel.DelegatingQuery.updateAll(
> DelegatingQuery.java:565)
>         at org.apache.openjpa.persistence.QueryImpl.executeUpdate(
> QueryImpl.java:314)
>         at org.apache.openjpa.persistence.query.TestSubQuery.testQuery(
> TestSubQuery.java:80)
>         ... 25 more
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Syntax
> error: Encountered "WHERE" at line 1, column 117. {UPDATE ORDERTB SET amount
> = (CAST(amount AS DOUBLE) + CAST(? AS DOUBLE)) WHERE oid IN (SELECT DISTINCT
> t2.oid FROM  WHERE (NOT (t2.oid IN (SELECT t1.oid FROM  WHERE t0.cid =
> t1.customer_cid))))} [code=20000, state=42X01]
>         at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(
> LoggingConnectionDecorator.java:200)
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$000(
> LoggingConnectionDecorator.java:56)
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection.prepareStatement
> (LoggingConnectionDecorator.java:227)
>         at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(
> DelegatingConnection.java:163)
>         at
> org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.prepareStatement
> (ConfiguringConnectionDecorator.java:140)
>         at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(
> DelegatingConnection.java:163)
>         at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$RefCountConnection.prepareStatement
> (JDBCStoreManager.java:1308)
>         at
> org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(
> DelegatingConnection.java:152)
>         at org.apache.openjpa.jdbc.sql.SQLBuffer.prepareStatement(
> SQLBuffer.java:474)
>         at org.apache.openjpa.jdbc.sql.SQLBuffer.prepareStatement(
> SQLBuffer.java:454)
>         at org.apache.openjpa.jdbc.sql.SQLBuffer.prepareStatement(
> SQLBuffer.java:443)
>         at
> org.apache.openjpa.jdbc.kernel.JDBCStoreQuery.executeBulkOperation(
> JDBCStoreQuery.java:500)
>         ... 34 more
>
> Running org.apache.openjpa.persistence.relations.TestLRS
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.171 sec
> Running
> org.apache.openjpa.persistence.relations.TestTargetedIFaceRelations
> 2  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 22  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.461 sec
> Running org.apache.openjpa.jdbc.kernel.TestNoForeignKeyViolation
> 6  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 7  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 10  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.386 sec
> Running org.apache.openjpa.conf.TestBadAutoDetachProperty
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 sec
> Running org.apache.openjpa.persistence.xml.TestSimpleXmlEntity
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 0  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.261 sec
> Running
> org.apache.openjpa.persistence.inheritance.TestMultipleMappedSuperclassHierarchy
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 10  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.199 sec
> Running org.apache.openjpa.persistence.identity.TestGenerationType
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 5  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 13  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 0  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 10  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 16  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.621 sec
> Running org.apache.openjpa.persistence.relations.TestIdOrderedOneMany
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 9  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.905 sec
> Running
> org.apache.openjpa.persistence.callbacks.TestExceptionsFromCallbacks
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 15  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 2  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 6  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.665 sec
> Running org.apache.openjpa.persistence.identity.TestFloatingPointIds
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 60.976 sec
> Running
> org.apache.openjpa.persistence.inheritance.TestSharedUnqualifiedClassNames
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 0  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 5  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.554 sec
> Running
> org.apache.openjpa.persistence.models.company.idclass.TestIdClassCompanyModel
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.177 sec
> Running org.apache.openjpa.jdbc.meta.TestMappingToolAutoDelete
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 2  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 6  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 27  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 101  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 372  test  INFO   [main] openjpa.Tool - No targets were given.  Running on
> all classes listed in your configuration, or all persistent classes in the
> classpath if no classes are configured.  Use -help to display tool usage
> information.
> 373  test  INFO   [main] openjpa.Tool - Mapping tool running on type
> "class org.apache.openjpa.persistence.xml.SimpleXmlEntity" with action
> "buildSchema".
> 619  test  INFO   [main] openjpa.Tool - Mapping tool running on type
> "class org.apache.openjpa.persistence.xml.XmlOverrideEntity" with action
> "buildSchema".
> 620  test  INFO   [main] openjpa.Tool - Mapping tool running on type
> "class org.apache.openjpa.persistence.simple.AllFieldTypes" with action
> "buildSchema".
> 623  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 623  test  INFO   [main] openjpa.Tool - Recording mapping and schema
> changes.
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.685 sec
> Running org.apache.openjpa.persistence.query.TestInMemoryQueryMatchEscapes
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 20  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 60  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 19  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 56  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 59  test  INFO   [main] openjpa.Query - This query on type "class
> org.apache.openjpa.persistence.simple.AllFieldTypes" must load the entire
> candidate class extent and evaluate the query in-memory.  This may be very
> slow.  The query must be executed in memory because OpenJPA is configured
> with IgnoreCache=false and FlushBeforeQueries=false and there are dirty
> instances that may affect the query's outcome in the cache.
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.55 sec
> Running
> org.apache.openjpa.persistence.datacache.TestArrayFieldsInDataCache
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 0  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 53  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 110  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 3  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 17  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 46  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.298 sec
> Running org.apache.openjpa.persistence.datacache.TestBulkJPQLAndDataCache
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 45  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 758  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 1  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 4  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 41  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 95  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 1  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 3  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to the
> database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 7  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> 25  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> 91  test  WARN   [main] openjpa.MetaData - OpenJPA cannot map field "
> org.apache.openjpa.persistence.simple.AllFieldTypes.arrayOfInts"
> efficiently.  It is of an unsupported type. The field value will be
> serialized to a BLOB by default.
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.176 sec
> Running org.apache.openjpa.persistence.xml.TestXmlOverrideEntity
> 0  test  INFO   [main] openjpa.Runtime - Starting OpenJPA 0.0.0
> 13  test  INFO   [main] openjpa.jdbc.JDBC - OpenJPA will now connect to
> the database to attempt to determine what type of database dictionary to
> use.  To prevent this connection in the future, set your
> openjpa.jdbc.DBDictionary configuration property to the appropriate value
> for your database (see the documentation for available values).
> 35  test  INFO   [main] openjpa.jdbc.JDBC - Using dictionary class "
> org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby 10.2.2.0 -
> (485682) ,Apache Derby Embedded JDBC Driver 10.2.2.0 - (485682)).
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0,...
>
> [Message clipped]

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message