[hibernate-dev] JIRA + FishEye
Just wanted to point out that the folks at Atlassian were kind enough to enable and setup the plugin to integrate JIRA and FishEye for us. This can be seen in 2 places: 1) on the project main screen, there is now a FishEye panel for commit information pertaining to the project as a whole 2) each issue has a FishEye tab to see commits relevant to that issue (based on message key in the commit messages). They would like feedback; so if you feel inclined and notice anything interesting, let me know and I'll pass it along. Thanks, Steve ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate as JPA persistence-provider in SAP Netweaver
On Friday 31 August 2007 01:27:24 am De Silva Jayasinghe, Robin wrote: > Hi Steve! > > > We are aware that the Hibernate SessionFactory attempts to obtain a > > Connection during its construction in order to query the JDBC metadata, > > yes. > > > > I think you may be slightly confused (it seems that way to me anyway). > > The connection obtained during construction of a SessionFactory has > > absolutely nothing to do with the connections used by sessions. > > I accept the fact that the connection obtained by SessionFactory is in no > relation to the one used by the Session. However, Table 2 in chapter 4.5.2 > of "EJB 3.0 Core Contracts and Requirements" states that during dependency > injection in a SLSB the access to ResourceManager is not allowed. We > interpret this part of the spec in a way that a SLSB is not allowed to > access to any resources (including datasources). Of course we accept the > fact that you might interpret the spec in a different way. I only want to > raise some awareness that Hibernate in its current state does not run as > smooth as it could on Netweaver. > > Best Regards, > Robin > > -- AFAICT, this is caused by your (atypical) decision to create the SessionFactory (EntityManagerFactory) upon first injection. If the SessionFactory were created up front at app start-up (which is by far more typical) you'd not have any issue. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] HHH-16...
All, I would like to get this thing working (the join ... on ... syntax stuff). I have begun work on it already (got a build working, started digging into ANTLR grammar, etc.), but I would appreciate any guidance that you folks could provide. I started by adding a couple of test cases and trying to figure out where in the heck this stuff goes haywire! Right now, I'm looking into the SqlGenerator class as it seems that's where the meat of this is going to be. I'm not an ANTLR expert, so that's probably been taking me the most time to wrap my head around. Again, any help you guys can provide would be greatly appreciated, both by me and my client, since they're footing the bill for this development effort (we need it on our project). James ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Old vs. New Query Translators?
For new functionality (such as HHH-16), do we need to make sure it
works the "old" way? I added a test case to HqlTest:
public void testExplicitJoinOnUnrelatedClasses() {
// HHH-16: Explicit joins on unrelated classes
assertTranslation("from Human h join Pet p on p.name = h.name");
}
The assertTranslation() method runs the query through both the old and
the new QueryTranslator implementations. The AST-based query
translator works for me now that I've altered the ANTLR grammar, but
the old one doesn't work (for obvious reasons). In order to get this
stuff working, we need to fix both the old and the new ones?
James
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] HHH-16...
On Wednesday 05 September 2007 01:48:31 pm James Carman wrote: > All, > > I would like to get this thing working (the join ... on ... syntax > stuff). I have begun work on it already (got a build working, started > digging into ANTLR grammar, etc.), but I would appreciate any guidance > that you folks could provide. I started by adding a couple of test > cases and trying to figure out where in the heck this stuff goes > haywire! Right now, I'm looking into the SqlGenerator class as it > seems that's where the meat of this is going to be. I'm not an ANTLR > expert, so that's probably been taking me the most time to wrap my > head around. Again, any help you guys can provide would be greatly > appreciated, both by me and my client, since they're footing the bill > for this development effort (we need it on our project). > > James > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev The very first thing I would do is to split the roles currently filled by FromElement into two separate node types (one for the join and one for the persister reference) because currently this is all munged together. It'll make this easier to work with. The big difficulty is somehow tracking the property references as they are being resolved so that you know what is the right side and left side of the join. This whole problem is easier to solve when we move from 3 phases to 4 phases, which is the reason this was put on the back burner in the first place. There is a branch where i started prototyping some of this work: http://anonsvn.jboss.org/repos/hibernate/core/branches/HQL_ANTLR_2/ You might want to take a look there for some ideas. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Old vs. New Query Translators?
On Wednesday 05 September 2007 02:14:55 pm James Carman wrote:
> For new functionality (such as HHH-16), do we need to make sure it
> works the "old" way? I added a test case to HqlTest:
>
> public void testExplicitJoinOnUnrelatedClasses() {
> // HHH-16: Explicit joins on unrelated classes
> assertTranslation("from Human h join Pet p on p.name = h.name");
> }
>
> The assertTranslation() method runs the query through both the old and
> the new QueryTranslator implementations. The AST-based query
> translator works for me now that I've altered the ANTLR grammar, but
> the old one doesn't work (for obvious reasons). In order to get this
> stuff working, we need to fix both the old and the new ones?
>
> James
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
It would not make sense for the old translator to understand this
functionality.
Such brand new features and syntaxes that the old translator did not
comprehend are not tested in org.hibernate.test.hql.HQLTest, but in
org.hibernate.test.hql.ASTParserLoadingTest. Have a look there.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] HHH-16...
The only reason I didn't go with the HQL_ANTLR_2 branch was that it wasn't "mavenized" at least as far as I could tell. That was the easiest way I could get a working project up and running within my IDE (mvn idea:idea). Could we fork off a branch from the mavenized trunk to do this work? Then we could work on it together if you've got some time to set up the 4-phase approach. On 9/5/07, Steve Ebersole <[EMAIL PROTECTED]> wrote: > On Wednesday 05 September 2007 01:48:31 pm James Carman wrote: > > All, > > > > I would like to get this thing working (the join ... on ... syntax > > stuff). I have begun work on it already (got a build working, started > > digging into ANTLR grammar, etc.), but I would appreciate any guidance > > that you folks could provide. I started by adding a couple of test > > cases and trying to figure out where in the heck this stuff goes > > haywire! Right now, I'm looking into the SqlGenerator class as it > > seems that's where the meat of this is going to be. I'm not an ANTLR > > expert, so that's probably been taking me the most time to wrap my > > head around. Again, any help you guys can provide would be greatly > > appreciated, both by me and my client, since they're footing the bill > > for this development effort (we need it on our project). > > > > James > > ___ > > hibernate-dev mailing list > > hibernate-dev@lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > The very first thing I would do is to split the roles currently filled by > FromElement into two separate node types (one for the join and one for the > persister reference) because currently this is all munged together. It'll > make this easier to work with. > > The big difficulty is somehow tracking the property references as they are > being resolved so that you know what is the right side and left side of the > join. > > This whole problem is easier to solve when we move from 3 phases to 4 phases, > which is the reason this was put on the back burner in the first place. > There is a branch where i started prototyping some of this work: > http://anonsvn.jboss.org/repos/hibernate/core/branches/HQL_ANTLR_2/ You > might want to take a look there for some ideas. > ___ > 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
[hibernate-dev] JBoss Cache 2.0 Integration
Hi Steve,
Need to touch base with you on the semantics for the JBC 2.0 integration.
1) QueryResultsRegionImpl
In the JBC 1.x impl, the get() and put() operations invoked from
StandardQueryCache suspended any tx before accessing the cache. In the
QueryResultsRegionImpl I've written I do the same, mostly to be consistent.
Good: Locks are not held in JBC for the life of a tx, so you don't get a
tx2 trying to read the cache blocking for a long-running tx1 that cached
a query result.
Bad: That tx2 can see the query results from tx1. Those results might
reflect uncommitted changes made by tx1.
Bad: The tx1 changes are replicated around the cluster as soon as they
are put in the cache, rather than at tx commit. More replication
messages, plus other nodes also see the uncommitted changes.
One possible solution I see to this is to not suspend the tx for put(),
and also pass a 0 ms timeout option to JBC for both get() and put().
Basically, don't block in the face of contention; just timeout and fail
silently. What do you think of this? (Doing this is going to require
addition of a new Option to JBC though.)
2) EntityRegionImpl
I noticed your impl of get() does not suspend any tx, which is different
from the old behavior. So, a get() call will cause a read lock in the
cache that will block any other tx doing an update. Was this intentional?
If it was intentional, it leads to an odd situation when putFromLoad is
called with minimalPutOverride=true
if ( minimalPutOverride && get( key, txTimestamp ) != null ) {
return false;
}
return putFromLoad( key, value, txTimestamp, version );
The get( key, txTimestamp ) call could block, while a regular
putFromLoad won't. So, if minimalPutOverride=true the call might block,
while if minimalPutOverride=false, it won't. That seems odd.
3) TimestampsRegionImpl
Here, suspending the tx on both get() and put() makes total sense. To
ensure the desired async replication though, I'm going to have to add a
new Option to JBC. Until that's done, the timestamps will replicate
synchronously if the timestamps cache is using the same cache as
entities/collections. :(
Good news here is I think I've solved an old problem where async
replication could result in timestamps going back in time.
TimestampsRegionImpl now maintains an internal timestamp map, and just
uses JBC as a replication layer. No change is allowed to the internal
timestamp map unless it *increases* the timestamp.
--
Brian Stansberry
Lead, AS Clustering
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] hibernate-sybase-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20070905215954 TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:126: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/05/2007 21:59:54Time to build: 18 minutes 6 secondsLast changed: 12/30/2005 15:59:42Last log entry: Fixed BMT idiom Unit Tests: (1079) Total Errors and Failures: (49)testOrphanDeleteOnDeleteorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestOrphanDeleteAfterPersistorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestOrphanDeleteAfterPersistAndFlushorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestOrphanDeleteAfterLockorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestOrphanDeleteOnSaveOrUpdateorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestOrphanDeleteOnSaveOrUpdateAfterSerializationorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestOrphanDeleteorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestOrphanDeleteOnMergeorg.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTesttestComponentQueriesorg.hibernate.test.component.basic.ComponentTesttestSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResourcesorg.hibernate.test.connections.AggressiveReleaseTesttestSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResourcesorg.hibernate.test.connections.CurrentSessionConnectionTesttestSubselectorg.hibernate.test.criteria.CriteriaQueryTesttestDom4jorg.hibernate.test.entitymode.dom4j.basic.Dom4jTesttestMapIndexEmisionorg.hibernate.test.entitymode.dom4j.basic.Dom4jTesttestStrorg.hibernate.test.hql.ASTParserLoadingTesttestExtractorg.hibernate.test.hql.ASTParserLoadingTesttestEJBQLFunctionsorg.hibernate.test.hql.ASTParserLoadingTesttestInterfaceProxiesorg.hibernate.test.interfaceproxy.InterfaceProxyTesttestJpaStylePositionalParametersInNativeSqlorg.hibernate.test.jpa.ql.NativeQueryTesttestOnCascadeDeleteorg.hibernate.test.legacy.FooBarTesttestCollectionsInSelectorg.hibernate.test.legacy.FooBarTesttestCompositeKeyPathExpressionsorg.hibernate.test.legacy.FumTesttestUnionSubclassorg.hibernate.test.legacy.IJ2TesttestCollectionorg.hibernate.test.legacy.MultiTableTesttestProxyReuseorg.hibernate.test.legacy.ParentChildTesttestBlobCloborg.hibernate.test.legacy.SQLFunctionsTesttestBoundedMaterializedBlobAccessorg.hibernate.test.lob.BlobTesttestBoundedBlobLocatorAccessorg.hibernate.test.lob.BlobTesttestUnboundedBlobLocatorAccessorg.hibernate.test.lob.BlobTesttestBoundedMaterializedClobAccessorg.hibernate.test.lob.ClobTesttestBoundedClobLocatorAccessorg.hibernate.test.lob.ClobTesttestUnboundedClobLocatorAccessorg.hibernate.test.lob.ClobTesttestNewSerializableTypeorg.hibernate.test.lob.SerializableTypeTesttestManyToManyWithFormulaorg.hibernate.test.manytomany.ManyToManyTesttestMixedInheritanceorg.hibernate.test.mixed.MixedTesttestOneToOneOnSubclassorg.hibernate.test.onetoone.joined.JoinedSubclassOneToOneTesttestOneToOneOnSubclassorg.hibernate.test.onetoone.nopojo.DynamicMapOneToOneTesttestPaginationorg.hibernate.test.pagination.PaginationTesttestOneToOnePropertyReforg.hibernate.test.propertyref.inheritence.union.UnionSubclassPropertyRefTesttestScalarStoredProcedureorg.hibernate.test.sql.hand.custom.sybase.SybaseCustomSQLTesttestParameterHandlingorg.hibernate.test.sql.hand.custom.sybase.SybaseCustomSQLTesttestEntityStoredProcedureorg.hibernate.test.sql.hand.custom.sybase.SybaseCustomSQLTesttestMappedAliasStrategyorg.hibernate.test.sql.hand.query.NativeSQLQueriesTesttestAutoDetectAliasingorg.hibernate.test.sql.hand.query.NativeSQLQueriesTesttestQueryStatGatheringorg.hibernate.test.stats.StatsTesttestCurrentSessionWithScrollorg.hibernate.test.tm.CMTTesttestUnionSubclassFetchModeorg.hibernate.test.unionsubclass.UnionSubclassTesttestJoinedSubclassorg.hibernate.test.ondelete.OnDeleteTesttestQueryCacheInvalidationorg.hibernate.test.querycache.QueryCacheTest Modifications since last build: (first 50 of 368)13961modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/impl/IteratorImpl.javaHHH-2728 : session.clear() while retrieving objects via an iterator fix that should work for all dialects13956modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/reattachment/ProxyReattachmentTest.javaHHH-2728 : session.clear() while retrieving objects via an iterator 13956modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/impl/Iterator
[hibernate-dev] hibernate-mysql-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20070905224405 TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:147: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/05/2007 22:44:05Time to build: 19 minutes 2 secondsLast changed: 12/30/2005 15:59:42Last log entry: Fixed BMT idiom Unit Tests: (1079) Total Errors and Failures: (6)testDom4jorg.hibernate.test.entitymode.dom4j.basic.Dom4jTesttestMapIndexEmisionorg.hibernate.test.entitymode.dom4j.basic.Dom4jTesttestPaginationorg.hibernate.test.pagination.PaginationTesttestScalarStoredProcedureorg.hibernate.test.sql.hand.custom.mysql.MySQLCustomSQLTesttestParameterHandlingorg.hibernate.test.sql.hand.custom.mysql.MySQLCustomSQLTesttestEntityStoredProcedureorg.hibernate.test.sql.hand.custom.mysql.MySQLCustomSQLTest Modifications since last build: (first 50 of 368)13961modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/impl/IteratorImpl.javaHHH-2728 : session.clear() while retrieving objects via an iterator fix that should work for all dialects13956modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/reattachment/ProxyReattachmentTest.javaHHH-2728 : session.clear() while retrieving objects via an iterator 13956modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/impl/IteratorImpl.javaHHH-2728 : session.clear() while retrieving objects via an iterator 13951modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/engine/loading/LoadContexts.javaHHH-2563 : Reversed log messages in LoadContexts.locateLoadingCollectionEntry(CollectionKey key)13936modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/engine/loading/LoadContexts.javaHHH-2795 : CollectionLoadContext processing for empty collections 13936modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/engine/loading/CollectionLoadContext.javaHHH-2795 : CollectionLoadContext processing for empty collections 13932modified[EMAIL PROTECTED]//core/branches/Branch_3_2/test/org/hibernate/test/legacy/MasterDetailTest.javaskip org.hibernate.test.legacy.MasterDetailTest#testCachedCollectionRefresh when connection is enforcing (at least) serializable isolation13932modified[EMAIL PROTECTED]//core/branches/Branch_3_2/test/org/hibernate/junit/functional/FunctionalTestCase.javaskip org.hibernate.test.legacy.MasterDetailTest#testCachedCollectionRefresh when connection is enforcing (at least) serializable isolation12949modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/persister/entity/AbstractEntityPersister.javaHHH-2503 : Throws JDBCExceptionHelper.convert() in AbstractEntityPersister.processGeneratedProperties()12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/OptionalJoinTest.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/persister/entity/AbstractEntityPersister.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/JoinSuite.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/Thing.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/AllTests.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/Thing.hbm.xmlHHH-2320 : Update detached entity with null joined properties changed to non-null12941modified[EMAIL PROTECTED]//core/branches/Branch_3_2/src/org/hibernate/dialect/Oracle8iDialect.javaHHH-2788 : missing type mapping for DATE and TIME on Oracle8iDialect12936modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/component/basic/Employee.javaHHH-2542 : Merge non-null component in a child persisted with a null component and added test for optional components12936modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/type/TypeFactory.javaHHH-2542 : Merge non-null component in a child persisted with a null component and added test for optional components12936modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/component/basic/ComponentTest.javaHHH-2542 : Merge non-null component in a child persisted with a null component and added test for optional components12936modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/
[hibernate-dev] hibernate-db2-8.2-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-db2-8.2-testsuite?log=log20070905232624 TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:178: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/05/2007 23:26:24Time to build: 38 minutes 27 secondsLast changed: 08/29/2007 19:00:10Last log entry: HHH-2728 : session.clear() while retrieving objects via an iterator fix that should work for all dialects Unit Tests: (1070) Total Errors and Failures: (12)testExpressionWithParamInFunctionorg.hibernate.test.hql.ASTParserLoadingTesttestDecimalLiteralsorg.hibernate.test.hql.ASTParserLoadingTesttestInsertWithGeneratedTimestampVersionorg.hibernate.test.hql.BulkManipulationTesttestScrollingJoinFetchesForwardorg.hibernate.test.hql.ScrollableCollectionFetchingTestunknownorg.hibernate.test.jpa.lock.JPALockTesttestCriteriaorg.hibernate.test.legacy.MultiTableTesttestBoundedClobLocatorAccessorg.hibernate.test.lob.ClobTesttestScalarStoredProcedureorg.hibernate.test.sql.hand.custom.db2.DB2CustomSQLTesttestParameterHandlingorg.hibernate.test.sql.hand.custom.db2.DB2CustomSQLTesttestEntityStoredProcedureorg.hibernate.test.sql.hand.custom.db2.DB2CustomSQLTestunknownorg.hibernate.test.tm.CMTTesttestBoundedBlobLocatorAccessorg.hibernate.test.lob.BlobTest Modifications since last build: (first 50 of 83)13961modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/impl/IteratorImpl.javaHHH-2728 : session.clear() while retrieving objects via an iterator fix that should work for all dialects13956modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/reattachment/ProxyReattachmentTest.javaHHH-2728 : session.clear() while retrieving objects via an iterator 13956modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/impl/IteratorImpl.javaHHH-2728 : session.clear() while retrieving objects via an iterator 13951modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/engine/loading/LoadContexts.javaHHH-2563 : Reversed log messages in LoadContexts.locateLoadingCollectionEntry(CollectionKey key)13936modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/engine/loading/LoadContexts.javaHHH-2795 : CollectionLoadContext processing for empty collections 13936modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/engine/loading/CollectionLoadContext.javaHHH-2795 : CollectionLoadContext processing for empty collections 13932modified[EMAIL PROTECTED]//core/branches/Branch_3_2/test/org/hibernate/test/legacy/MasterDetailTest.javaskip org.hibernate.test.legacy.MasterDetailTest#testCachedCollectionRefresh when connection is enforcing (at least) serializable isolation13932modified[EMAIL PROTECTED]//core/branches/Branch_3_2/test/org/hibernate/junit/functional/FunctionalTestCase.javaskip org.hibernate.test.legacy.MasterDetailTest#testCachedCollectionRefresh when connection is enforcing (at least) serializable isolation12949modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/persister/entity/AbstractEntityPersister.javaHHH-2503 : Throws JDBCExceptionHelper.convert() in AbstractEntityPersister.processGeneratedProperties()12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/OptionalJoinTest.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945modifiedgbadner//core/branches/Branch_3_2/src/org/hibernate/persister/entity/AbstractEntityPersister.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/JoinSuite.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/Thing.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/AllTests.javaHHH-2320 : Update detached entity with null joined properties changed to non-null12945addedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/join/Thing.hbm.xmlHHH-2320 : Update detached entity with null joined properties changed to non-null12941modified[EMAIL PROTECTED]//core/branches/Branch_3_2/src/org/hibernate/dialect/Oracle8iDialect.javaHHH-2788 : missing type mapping for DATE and TIME on Oracle8iDialect12936modifiedgbadner//core/branches/Branch_3_2/test/org/hibernate/test/component/basic/Employee.javaHHH-2542 : Merge non-null component in a child persisted with a null component and added test for optional components12936modifiedgbadner//core/branches/Bran
[hibernate-dev] hibernate-oracle9-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle9-testsuite?log=log20070906005650 TESTS FAILEDAnt Error Message: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:112: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:89: The following error occurred while executing this line: /qa/services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 09/06/2007 00:56:50Time to build: 13 minutes 57 seconds Unit Tests: (1079) Total Errors and Failures: (2)testReadOnlyModeorg.hibernate.test.readonly.ReadOnlyTesttestOrderByorg.hibernate.test.sorted.SortTest Modifications since last build: (first 50 of 0) ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
