[Hibernate-JIRA] Created: (HHH-2418) Refer HSQL DB website in chapter 1.2.3
by Diego Pires Plentz (JIRA)
Refer HSQL DB website in chapter 1.2.3
--------------------------------------
Key: HHH-2418
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2418
Project: Hibernate3
Type: Improvement
Components: documentation
Versions: 3.2.2
Reporter: Diego Pires Plentz
"1.2.3. Hibernate configuration
We now have a persistent class and its mapping file in place. It is time to configure Hibernate. Before we do this, we will need a database. HSQL DB, a java-based SQL DBMS, can be downloaded from the HSQL DB website. Actually, you only need the hsqldb.jar from this download. Place this file in the lib/ directory of the development folder. "
to
"1.2.3. Hibernate configuration
We now have a persistent class and its mapping file in place. It is time to configure Hibernate. Before we do this, we will need a database. HSQL DB, a java-based SQL DBMS, can be downloaded from the HSQL DB website(http://hsqldb.org/). Actually, you only need the hsqldb.jar from this download. Place this file in the lib/ directory of the development folder. "
--
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
17 years, 5 months
[Hibernate-JIRA] Created: (HHH-2420) Error in 2.5. Contextual Sessions
by Diego Pires Plentz (JIRA)
Error in 2.5. Contextual Sessions
---------------------------------
Key: HHH-2420
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2420
Project: Hibernate3
Type: Improvement
Components: documentation
Reporter: Diego Pires Plentz
"Typically, the value of this parameter would just name the implementation class to use; for the three out-of-the-box implementations, however, there are **two** corresponding short names, "jta", "thread", and "managed"."
should be
"Typically, the value of this parameter would just name the implementation class to use; for the three out-of-the-box implementations, however, there are three corresponding short names, "jta", "thread", and "managed"."
--
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
17 years, 5 months
[Hibernate-JIRA] Created: (HBX-945) CLONE -hbm2java does not generate correct POJO property types for UserType columns
by Brill Pappin (JIRA)
CLONE -hbm2java does not generate correct POJO property types for UserType columns
----------------------------------------------------------------------------------
Key: HBX-945
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-945
Project: Hibernate Tools
Issue Type: Bug
Components: hbm2java
Affects Versions: 3.1alpha5
Environment: Pulled from CVS somewhere between 3.1a5 and 3.1b1
Reporter: Brill Pappin
Fix For: 3.1beta2
I have defined my own custom UserType (which coincidentally maps a DB2 decimal field to a java.sql.Date property, using some special formatting...).
My mapping file contains:
<property name="connectDate" type="DecimalDateType">
<column name="UMPCN" precision="8" scale="0" not-null="true" />
</property>
where DecimalDateType is the fully-qualified name of my UserType class.
The POJO generated contains the property:
private DecimalDateType connectDate;
This is incorrect. It SHOULD have generated a property of the type returned by DecimalDateType.returnedClass() (which in this case is java.sql.Date.class). ie. It should have been
private java.sql.Date connectDate;
The "decision" of which type to generate (ie where the error manifests itself) error appears to be in
Cfg2JavaTool.java
in the method
private String getJavaTypeName(Value value, boolean preferRawTypeNames)
I am not sure of the exact fix, since there appear to be other checks being done, and I do not understand all the logic here.
Thanks!
james
--
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
17 years, 5 months
[Hibernate-JIRA] Created: (HHH-2160) JTATransactionFactory.isTransactionInProgress fails with WebSphereExtendedJTATransactionLookup
by Timothy Folks (JIRA)
JTATransactionFactory.isTransactionInProgress fails with WebSphereExtendedJTATransactionLookup
----------------------------------------------------------------------------------------------
Key: HHH-2160
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2160
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.ga
Environment: Hibernate 3.2.0 ga
WebSphere Application Server 6.0.2.15
DB2 9.1
Reporter: Timothy Folks
Configurating Hibernate with the following settings:
hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory
hibernate.transaction.manager_lookup_class=org.hibernate.transaction.WebSphereExtendedJTATransactionLookup
jta.UserTransaction=java:comp/UserTransaction
hibernate.current_session_context_class=jta
results in the following stack trace (irrelevant lines snipped)
<snipped>
Caused by: org.hibernate.TransactionException: could not register synchronization with JTA TransactionManager
at org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible(JDBCContext.java:181)
at org.hibernate.jdbc.JDBCContext.<init>(JDBCContext.java:76)
at org.hibernate.impl.SessionImpl.<init>(SessionImpl.java:213)
at org.hibernate.impl.SessionFactoryImpl.openSession(SessionFactoryImpl.java:525)
at org.hibernate.context.JTASessionContext.buildOrObtainSession(JTASessionContext.java:114)
at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:80)
at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:542)
<snipped>
Caused by: java.lang.UnsupportedOperationException
at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(WebSphereExtendedJTATransactionLookup.java:78)
at org.hibernate.transaction.JTATransactionFactory.isTransactionInProgress(JTATransactionFactory.java:94)
at org.hibernate.jdbc.JDBCContext.isTransactionInProgress(JDBCContext.java:187)
at org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible(JDBCContext.java:159)
The workaround I've implemented is to change the following line in JTATransactionFactory.isTransactionInProgress:
if ( jdbcContext.getFactory().getTransactionManager() != null ) {
to:
if ( jdbcContext.getFactory().getTransactionManager() != null && jdbcContext.getFactory().getTransactionManager() instanceof WebSphereExtendedJTATransactionLookup.TransactionManagerAdapter == false) {
This results in the method falling back to looking up the UserTransaction in JNDI and calling getStatus on that.
--
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
17 years, 5 months