Support legacy TransactionFactory names
---------------------------------------
Key: HHH-5619
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5619
Project: Hibernate Core
Issue Type: Task
Components: core
Reporter: Steve Ebersole
Assignee: Gail Badner
Fix For: 4.0.0.Alpha1
In the short term interest of migration, have the Transactionfactory service initiator recognize the legacy class names in addition to the new names
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add support for a programmatic way to define a default EntityPersister and CollectionPersister class implementation
-------------------------------------------------------------------------------------------------------------------
Key: HHH-5916
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5916
Project: Hibernate Core
Issue Type: New Feature
Reporter: Emmanuel Bernard
Assignee: Emmanuel Bernard
Fix For: 3.6.2, 4.0.0.Alpha1
It is useful for OGM.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Extract SQL keywords from DatabaseMetaData
------------------------------------------
Key: HHH-5687
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5687
Project: Hibernate Core
Issue Type: New Feature
Components: core
Reporter: Steve Ebersole
Fix For: 4.0.0.Alpha1
{{java.sql.DatabaseMetaData.html#getSQLKeywords}} is defined to return the (comma separated list of) keywords for the given database above-and-beyond the set of standard (SQL 2003) keywords. We should leverage this information while we build the JbdcServices to build out a fuller picture of database keywords to allow Dialect developers a choice between defining keywords themselves versus utilizing the extracted information.
This would become part of the {{org.hibernate.engine.jdbc.spi.ExtractedDatabaseMetaData}}.
The list of SQL 2003 keywords can be found at http://savage.net.au/SQL/sql-2003-2.bnf.html#xref-keywords
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Migrate, complete and integrate TransactionFactory as a service
---------------------------------------------------------------
Key: HHH-5949
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5949
Project: Hibernate Core
Issue Type: Task
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 4.0.0.Alpha1
Migrate and finalize the work done t implement TransactionFactory as a Service from the SourceForge Hibernate Git repo. Then integrate it into SessionFactory et al.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Failing tests hide the assertion failure message by consequently failing cleanup methods
----------------------------------------------------------------------------------------
Key: HSEARCH-686
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-686
Project: Hibernate Search
Issue Type: Bug
Reporter: Sanne Grinovero
Assignee: Hardy Ferentschik
Priority: Minor
Fix For: 3.4.0
It seems that if a Search test fails in the testmethod, the stacktrace and error messages are hidden by cleanup methods which are invoked by parent test logic, which also fail as the SessionFactory is closed and resources such as DirectoryProviders are already closed so they fail to cleanup data and hide the true issue.
If a test does not fail, nothing wrong happens.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira