[hibernate-dev] hibernate-oracle10-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20060811022928 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:101: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:78: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 08/11/2006 02:29:28Time to build: 17 minutes 20 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (880) Total Errors and Failures: (3)testSequenceIdentityGeneratororg.hibernate.test.generatedkeys.seqidentity.SequenceIdentityTesttestSelectWithDistinctClauseorg.hibernate.test.jpa.ql.JPAQLComplianceTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTest Modifications since last build: (first 50 of 1765)10238modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/basic_mapping.xmlI've finished translating reference document v3.2.0 at last : )10238modifiedhonma//trunk/Hibernate3/doc/reference/ja/readme_ja.txtI've finished translating reference document v3.2.0 at last : )10238modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/architecture.xmlI've finished translating reference document v3.2.0 at last : )10238modifiedhonma//trunk/Hibernate3/doc/reference/ja/master.xmlI've finished translating reference document v3.2.0 at last : )10238modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/tutorial.xmlI've finished translating reference document v3.2.0 at last : )10238modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/query_sql.xmlI've finished translating reference document v3.2.0 at last : )10237modifiedepbernard//trunk/Hibernate3/src/org/hibernate/engine/CascadingAction.javaHHH-1992 avoid cascading checking on lazy properties if it does not make sense10237modifiedepbernard//trunk/Hibernate3/src/org/hibernate/engine/Cascade.javaHHH-1992 avoid cascading checking on lazy properties if it does not make sense10229modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/legacy/Glarch.hbm.xmlHHH-1980 : disallow combination of and optimistic-lock10229modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/tuple/entity/EntityMetamodel.javaHHH-1980 : disallow combination of and optimistic-lock10228modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/AbstractEntityPersister.javatemporary fix for HHH-198010226modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/AbstractEntityPersister.javaHHH-1677 : optimistic-lock and delete10226modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/optlock/OptimisticLockTest.javaHHH-1677 : optimistic-lock and delete10226modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/sql/Delete.javaHHH-1677 : optimistic-lock and delete10226modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/optlock/Document.hbm.xmlHHH-1677 : optimistic-lock and delete10224modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/event/def/DefaultEvictEventListener.javaHHH-1954 : proxies and eviction10223modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/proxy/Container.javaHHH-1954 : proxies and eviction10223modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/proxy/DataPoint.javaHHH-1954 : proxies and eviction10223modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/proxy/DataPoint.hbm.xmlHHH-1954 : proxies and eviction10223added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/proxy/Info.javaHHH-1954 : proxies and eviction10223modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/proxy/ProxyTest.javaHHH-1954 : proxies and eviction10222modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/DerbyDialect.javamissed import cleanup10221modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/Dialect.javaadded ResultColumnReferenceStrategy (not yet being utilized);Derby trim() function (w/o capability to specify replacement character)10221modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/DerbyDialect.javaadded ResultColumnReferenceStrategy (not yet being utilized);Derby trim() function (w/o capability to specify replacement character)10221added[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/ResultColumnReferenceStrategy.javaadded ResultColumnReferenceStrategy (not yet being utilized);Derby trim() function (w/o capability to specify replacement character)10221deleted[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/function/AnsiTrimEmulationFunction.javaadded ResultColumnReferenceStrategy (not yet being utilized);Derby trim() function (w/o capability to specify repla
Re: [hibernate-dev] Does anybody read this list? Esp Steve
The last dev related mail I got from you is the one regarding the SecondPass Max Rydahl Andersen wrote: I have the same feeling ;) Did my follow up on the byteinstrumentation and ant task make it out to you guys ? OK so you intentionally do not reply to my emails ;-) Steve Ebersole wrote: I still read both as of right now. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Wednesday, August 09, 2006 4:28 PM To: hibernate-dev@lists.jboss.org Subject: [hibernate-dev] Does anybody read this list? Esp Steve Since the list system change, does anybody see it hibernate-dev@lists.jboss.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Does anybody read this list? Esp Steve
so this one never made it through ?: Another capability that I would like to see would be to limit instrumentation to only fields which are defined in a Hibernate mapping. Currently the instrument tasks do not know anything about the mappings, so the first change to allow this would be facilitate the passing or definition of a Configuration into the tasks. The tools already have such a task used in their ant task stacks. So we would need to decide whether it makes more sense to move the instrument tasks over to the tools subproject, or to consume the sub task from tools into core and make use of it from the instrument tasks. The "easiest" thing codewise is to move the instruments task to hibernate-tools, since the sourrounding task is the actual Ant entry point and the , , , etc. are defined in there. There is also the whole freemarker/templating setup dependency. ...thinking about it an alternative way could be to define a superclass for the current org.hibernate.tool.ant.HibernateToolTask that would just handle the core-built-in ant tasks. then users would have the same ant "API", but users would have to change their taskdef to use the "tool" provided tasks. Another context for this alignment/move is the talks we have had about allowing customization of schemaexport/update ...that would also be relevant to ensure it fits into this scheme. -- /max The last dev related mail I got from you is the one regarding the SecondPass Max Rydahl Andersen wrote: I have the same feeling ;) Did my follow up on the byteinstrumentation and ant task make it out to you guys ? OK so you intentionally do not reply to my emails ;-) Steve Ebersole wrote: I still read both as of right now. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Wednesday, August 09, 2006 4:28 PM To: hibernate-dev@lists.jboss.org Subject: [hibernate-dev] Does anybody read this list? Esp Steve Since the list system change, does anybody see it hibernate-dev@lists.jboss.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] RE: [Hibernate] Session.replicate() into IDENTITY table ?
StatelessSession has nothing to do with lack of a transaction!
- meaning StatelessSession operates in a transaction exactly as does
Session...
-Original Message-
From: Darryl Miles [mailto:[EMAIL PROTECTED]
Sent: Friday, August 11, 2006 3:13 AM
To: Steve Ebersole
Cc: hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] Session.replicate() into IDENTITY table ?
Steve Ebersole wrote:
> Not sure if anyone replied to this yet or not, so I'll throw my $0.02
> into the discussion. I think all that is needed is to better allow
> definition of what is to occur during replication in the method call.
> For example, consider the changing the signature from accepting a
> ReplicationMode to accepting a (new) "ReplicationStrategy", where
> ReplicationStrategy is defined something like:
> ReplicationStrategy {
> /**
> * How should we react when we encounter a pre-existing row
> * in the target database?
> *
> * TODO: probably rename the ReplicationMode class to MergeMode
> */
> public ReplicationMode getMergeMode() ...
> /**
> * When replicating an entity which does not yet occur in the
> * target database, should we enforce that the target data
> * we are about to create have the same identifier value?
> */
> public boolean forceIdentiferRetention() ...
> }
>
> Also, there has been some discussion about moving the replicate
> functionality from the Session interface to the StatelessSession
> interface which would be a good point in time to introduce such
changes.
The use of a strategy configuration object would fine from the Hibernate
API users perspective and head off the possibility of legacy API kruft
issues (when another parameter is wanted in the future).
Would I be correct in saying that operations using a StatelessSession
are not part of a transaction ? If so are you proposing to _REMOVE_ the
Session#replicate() operation completely that is part of a transaction.
Providing for both stateful and stateless would cover all bases and
have their valid use cases. Maybe I am misunderstanding something here.
Darryl
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate-mysql-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20060811222516 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:122: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:78: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 08/11/2006 22:25:16Time to build: 43 minutes 10 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (870) Total Errors and Failures: (44)testComponentQueriesorg.hibernate.test.hql.ASTParserLoadingTesttestCollectionFetchWithDistinctionAndLimitorg.hibernate.test.hql.ASTParserLoadingTesttestTempTableGenerationIsolationorg.hibernate.test.hql.BulkManipulationTesttestBooleanHandlingorg.hibernate.test.hql.BulkManipulationTesttestSimpleInsertorg.hibernate.test.hql.BulkManipulationTesttestSimpleNativeSQLInsertorg.hibernate.test.hql.BulkManipulationTesttestInsertWithManyToOneorg.hibernate.test.hql.BulkManipulationTesttestInsertWithMismatchedTypesorg.hibernate.test.hql.BulkManipulationTesttestInsertIntoSuperclassPropertiesFailsorg.hibernate.test.hql.BulkManipulationTesttestInsertAcrossMappedJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateWithWhereExistsSubqueryorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnComponentorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnImplicitJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnAnimalorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnMammalorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullUnionSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnMappedJoinorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassAbstractRootorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassConcreteSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassLeafSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteWithMetadataWhereFragmentsorg.hibernate.test.hql.BulkManipulationTesttestDeleteRestrictedOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestScrollingJoinFetchesForwardorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesReverseorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesPositioningorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestWithClauseFailsWithFetchorg.hibernate.test.hql.WithClauseTesttestWithClauseorg.hibernate.test.hql.WithClauseTesttestSelectWithDistinctClauseorg.hibernate.test.jpa.ql.JPAQLComplianceTesttestQueryorg.hibernate.test.legacy.FooBarTesttestOneToOneGeneratororg.hibernate.test.legacy.FooBarTesttestReachabilityorg.hibernate.test.legacy.FooBarTesttestVersionedCollectionsorg.hibernate.test.legacy.FooBarTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestOneToManyLinkTableorg.hibernate.test.onetomany.OneToManyTesttestAutoDetectAliasingorg.hibernate.test.sql.GeneralTesttestScalarStoredProcedureorg.hibernate.test.sql.MySQLTesttestParameterHandlingorg.hibernate.test.sql.MySQLTesttestEntityStoredProcedureorg.hibernate.test.sql.MySQLTest Modifications since last build: (first 50 of 1793)10251modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/SQLServerDialect.javautilize combined trim emulation function template from sqlserver dialect10249modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/DB2Dialect.javaHHH-1949 : ANSI SQL trim() function on DB2 and friends10249added[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/function/AnsiTrimEmulationFunction.javaHHH-1949 : ANSI SQL trim() function on DB2 and friends10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/TestIsPropertyInitializedExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/domain/Documents.hbm.xmlHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/TestLazyManyToOneExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10
[hibernate-dev] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20060811230923 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:87: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:78: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 08/11/2006 23:09:23Time to build: 8 minutes 46 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (872) Total Errors and Failures: (3)testSelectWithDistinctClauseorg.hibernate.test.jpa.ql.JPAQLComplianceTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestAutoDetectAliasingorg.hibernate.test.sql.GeneralTest Modifications since last build: (first 50 of 1793)10251modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/SQLServerDialect.javautilize combined trim emulation function template from sqlserver dialect10249modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/DB2Dialect.javaHHH-1949 : ANSI SQL trim() function on DB2 and friends10249added[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/dialect/function/AnsiTrimEmulationFunction.javaHHH-1949 : ANSI SQL trim() function on DB2 and friends10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/TestIsPropertyInitializedExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/domain/Documents.hbm.xmlHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/TestLazyManyToOneExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/TestInjectFieldInterceptorExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/AbstractExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/TestLazyExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/Executable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/TestIsPropertyInitializedExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/TestFetchAllExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/TestLazyManyToOneExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/TestManyToOneProxyExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246deleted[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/TestDirtyCheckExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/casesHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/JavassistInstrumentationTest.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/Executable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/cases/TestLazyExecutable.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/instrument/runtime/AbstractTransformingClassLoaderInstrumentTestCase.javaHHH-1740 : many-to-one (and one-to-one) with lazy="proxy" and bytecode instrumentation10246
[hibernate-dev] Mail list migration complete
Migration of the Hibernate email lists to their new hosting home is now complete. As of today, automated emails have been fully cut over: JIRA -> [EMAIL PROTECTED] SVN -> [EMAIL PROTECTED] CruiseControl -> hibernate-dev@lists.jboss.org For the past 2 weeks or so I have been monitoring both of the dev lists. As of next week, that will stop and I will only continue to subscribe to hibernate-dev@lists.jboss.org The [EMAIL PROTECTED] is new and we'll see how it goes. It is supposed to be used for general announcements, release notifications, etc. For example, I intend to send release announcements to both [EMAIL PROTECTED] and [EMAIL PROTECTED] Thanks! Steve ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
