March 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (HHH-1368) Transaction Manager LookUP class for Apache Geronimo Application server

by Jonas Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1368?page=c... ] Jonas Andersen updated HHH-1368: -------------------------------- Attachment: GeronimoTransactionManagerLookup.java Here is a transaction lookup class for Geronimo. I have only done very limited testing so far on Geronimo 2.0.2 and the Hibernate CMTTransactionFactory behind an EJB3 SLSB with CMT. The JNDI names should be the same for Geronimo 2.1. I have not checked earlier versions. The names used seems to be identical to those used in the JRun4TransactionManagerLookup, so if you don't mind the name being different, at least resolving the UserTransaction and TransactionManager should be possible with that class as well. > Transaction Manager LookUP class for Apache Geronimo Application server > ----------------------------------------------------------------------- > > Key: HHH-1368 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1368 > Project: Hibernate3 > Issue Type: New Feature > Components: core > Affects Versions: 3.0.5 > Environment: All versions, All Database platform > Reporter: Rakesh Ranjan > Priority: Minor > Attachments: GeronimoTransactionManagerLookup.java > > > Hibernate provides TransactionManager Lookup class for most of the J2EE application servers like Bea Weblogic, IBM Websphere, JBoss, Orion, Jrun. But there is no TransactionManager lookup class for Apache Geronimo Application server. Apache Geronimo is an emerging opensource J2EE application server. So we need to provide a TransactionManager lookup class for Apache Geronimo. -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-892) HQL parser does not resolve alias in ORDER BY clause

by Pierre (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-892?page=co... ] Pierre commented on HHH-892: ---------------------------- It would really nice to see a solution for this issue. The fact is on large slow query you don't want to repeat the subquery. Without a proper way to alias these subqueries, they bexome useless, at least if put in the select part of the query. The only solution is to switch back to SQL... > HQL parser does not resolve alias in ORDER BY clause > ----------------------------------------------------- > > Key: HHH-892 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-892 > Project: Hibernate3 > Issue Type: Bug > Components: query-hql > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5, MySQL, Tomcat > Reporter: Guido Laures > Priority: Minor > > When using an alias for an ORDER BY clause this is not always correctly resolved. Example: > SELECT SUM(A.x) AS mySum FROM MyClass AS A GROUP BY A.y ORDER BY mySum > does not work because "mySum" is not resolved in the ORDER BY clause which results in an exception telling that mySum is an unknown column. > Workaround (not to say "hack") is using: > SELECT SUM(A.x) AS mySum FROM MyClass AS A GROUP BY A.y ORDER BY col_0_0_ -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3200) Dialect auto-detection provides misleading error message

by Gino A Melone (JIRA)

Dialect auto-detection provides misleading error message -------------------------------------------------------- Key: HHH-3200 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3200 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6, 3.2.5 Environment: I'm testing with 3.2.5.ga, Windows XP SP2, and SQL Server 2000. However, I'm fairly certain this will affect any OS/DB combination. Reporter: Gino A Melone If the DB connection is unable to be created in org.hibernate.cfg.SettingsFactory.buildSettings(Properties props), the error message that is returned indicates "Hibernate Dialect must be explicitly set". This message is misleading. The real problem is that auto-detection can not work because the DB connection failed and the metadata could not be retrieved. A warning is issued that explains this, but production environments often disable log4j warnings for third-party packages to maintain reasonable-sized log files. The failure to create a connection should be used to generate a useful error message. Something like: //SQL Dialect: Dialect dialect = determineDialect( props, databaseName, databaseMajorVersion ); settings.setDialect(dialect); The relevant log entries are below. -- 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

18 years

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-345) compound primary/foreign key problems with nulls and NamedQuery parsing

by Reid Hartenbower (JIRA)

compound primary/foreign key problems with nulls and NamedQuery parsing ----------------------------------------------------------------------- Key: EJB-345 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-345 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.GA Environment: Hibernate core 3.2.6.ga, Hibernate EntityManager 3.3.2.GA, Hibernate Validator 3.0.0.GA, Hibernate Annotations 3.3.1.GA MySQL 5.0.45 / driver jar mysql-connector-java-3.1.12-bin Reporter: Reid Hartenbower Attachments: test-src.zip Hi. I have Item, Container, and Specification entities that subclass NamedThing. NamedThing uses a compound primary key which is a two-long representation of a UUID. Item has a @ManyToOne with Container and Specification, and Specification has a <String,String> properties map. Two problems, first: queries like "select distinct object(i) from Item i where i.specification.properties[:key] = :value" produce parse errors (these are the commented-out NamedQueries in Item); the complaint is '.' character after specification queries like "select distinct object(i) from Item i, Specification s where i.container is null and i.specification = s and s.properties[:key] is null" in TestItem.java:61 do parse successfully but produce the exception whose stack trace is in TestItemStackTrace.txt. The hibernate sql is in hibernate-sql-output.txt; the complaint is 'java.sql.SQLException: Operand should contain 1 column(s)' Thanks, Reid -- 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

18 years

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-217) Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported

by Michał Borowiecki (JIRA)

Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported ----------------------------------------------------------------------- Key: EJB-217 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-217 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.0.cr1 Environment: JBoss4.0.4.GA Reporter: Michał Borowiecki Having more than one relationship on en entity annotated with @OneToMany(fetch=FetchType.EAGER) causes exception when deploying the ejb3 module: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags. This bug is thoroughly explained here: http://www.jroller.com/page/eyallupu?entry=hibernate_exception_simultaneo... and depends on HHH-1718 "Have multiple bag fetches revert to subselect fetching for all but one of the bags" The temporary solution in HHH-1413 - disallowing multiple bag fetches is unsuitable to ejb3 environment, because the spec does not disallow it. -- 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

18 years

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-714) @NamedQuery always gives an Exception "unexpected token" no matter what query is used

by VPC (JIRA)

@NamedQuery always gives an Exception "unexpected token" no matter what query is used ------------------------------------------------------------------------------------- Key: ANN-714 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-714 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Windows XPP SP2, Weblogic Server wlserver_10.0, jdk150_11, Weblogic Workshop Reporter: VPC @Entity @Table(name="CONTACT") @NamedQueries({ @NamedQuery(name = "selectall", query = "SELECT * FROM CONTACT") }) public class Contact { ---usual setter getters---- } @NamedQuery annotation always throws the following exception at the following line: SessionFactory sessionFactory = new AnnotationConfiguration().configure().buildSessionFactory(); The stack trace of the exception is as follows: <Fri Mar 21 15:14:22 EDT 2008> <Info> <org.hibernate.tool.hbm2ddl.TableMetadata> <BEA-000000> <table found: hibernatetutorial.contact> <Fri Mar 21 15:14:22 EDT 2008> <Info> <org.hibernate.tool.hbm2ddl.TableMetadata> <BEA-000000> <columns: [lastname, firstname, email, id]> <Fri Mar 21 15:14:22 EDT 2008> <Info> <org.hibernate.tool.hbm2ddl.TableMetadata> <BEA-000000> <foreign keys: []> <Fri Mar 21 15:14:22 EDT 2008> <Info> <org.hibernate.tool.hbm2ddl.TableMetadata> <BEA-000000> <indexes: []> <Fri Mar 21 15:14:22 EDT 2008> <Info> <org.hibernate.tool.hbm2ddl.SchemaUpdate> <BEA-000000> <schema update complete> <Fri Mar 21 15:14:22 EDT 2008> <Trace> <org.hibernate.connection.DriverManagerConnectionProvider> <BEA-000000> <returning connection to pool, pool size: 1> <Fri Mar 21 15:14:22 EDT 2008> <Debug> <org.hibernate.impl.SessionFactoryImpl> <BEA-000000> <Checking 1 named HQL queries> <Fri Mar 21 15:14:22 EDT 2008> <Debug> <org.hibernate.impl.SessionFactoryImpl> <BEA-000000> <Checking named query: selectall> <Fri Mar 21 15:14:22 EDT 2008> <Trace> <org.hibernate.engine.query.QueryPlanCache> <BEA-000000> <unable to locate HQL query plan in cache; generating (SELECT * FROM CONTACT)> <Fri Mar 21 15:14:22 EDT 2008> <Debug> <org.hibernate.hql.ast.QueryTranslatorImpl> <BEA-000000> <parse() - HQL: SELECT * FROM CONTACT> <Fri Mar 21 15:14:22 EDT 2008> <Error> <org.hibernate.hql.PARSER> <BEA-000000> <line 1:8: unexpected token: *> <Fri Mar 21 15:14:22 EDT 2008> <Debug> <org.hibernate.hql.ast.ErrorCounter> <BEA-000000> <line 1:8: unexpected token: *> org.hibernate.HibernateException: Errors in named queries: selectall at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859) at hib.FirstExample.main(FirstExample.java:18) <Fri Mar 21 15:14:22 EDT 2008> <Debug> <org.hibernate.hql.ast.AST> <BEA-000000> <--- HQL AST --- \-[QUERY] 'query' \-[SELECT_FROM] 'SELECT_FROM' \-[FROM] 'FROM' \-[RANGE] 'RANGE' \-[IDENT] 'CONTACT' > <Fri Mar 21 15:14:22 EDT 2008> <Debug> <org.hibernate.impl.SessionFactoryImpl> <BEA-000000> <Checking 0 named SQL queries> <Fri Mar 21 15:14:22 EDT 2008> <Error> <org.hibernate.impl.SessionFactoryImpl> <BEA-000000> <Error in named query: selectall> -- 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

18 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3196) Dialect auto detection not documented?

by James Roper (JIRA)

Dialect auto detection not documented? -------------------------------------- Key: HHH-3196 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3196 Project: Hibernate3 Issue Type: Improvement Components: documentation Reporter: James Roper Priority: Trivial The documentation says: "You should always set the hibernate.dialect property to the correct org.hibernate.dialect.Dialect subclass for your database. If you specify a dialect, Hibernate will use sensible defaults for some of the other properties listed above, saving you the effort of specifying them manually." Is that still correct, or is it possible that this is left over from a time when Hibernate didn't support auto detecting dialects? Because I've noticed feature requests in JIRA for auto detecting dialects that were rejected, and I've noticed other JIRA issues that talk about adding dialects to the auto detection map. What is hibernates behavior when the dialect isn't specified? -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3194) Move/reschedule HHH-3077

by Stephen Kestle (JIRA)

Move/reschedule HHH-3077 ------------------------ Key: HHH-3194 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3194 Project: Hibernate3 Issue Type: Task Affects Versions: 3.3.0.CR1 Reporter: Stephen Kestle HHH-2748 was created as a subtask of HHH-2702. It was to do with removing calls to deprecated methods in apache's commons collections lib due to scheduled removal in the next version. I created HHH-3077 as another sub-task of HHH-2702, but have only just noticed that the parent ticket has been closed, which causes tracking issues in jira (hence HHH-3077 has not been seen or scheduled) Can we please get this scheduled? -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-42) Check Hibernate Search deployment in JBoss AS 4.2

by Emmanuel Bernard (JIRA)

Check Hibernate Search deployment in JBoss AS 4.2 ------------------------------------------------- Key: HSEARCH-42 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-42 Project: Hibernate Search Issue Type: Task Reporter: Emmanuel Bernard Christian had issues when HSearch and core jars are in server/default/lib rather than the application scope Check 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

18 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3193) Register Oracle's TIMESTAMPTZ (-101) in Oracle 9i Dialect

by Mark A. Ziesemer (JIRA)

Register Oracle's TIMESTAMPTZ (-101) in Oracle 9i Dialect --------------------------------------------------------- Key: HHH-3193 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3193 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Environment: Oracle 9i, Hibernate 3.2.6 Reporter: Mark A. Ziesemer I hate to resurrect the heated discussions at http://opensource.atlassian.com/projects/hibernate/browse/HHH-1893 and http://forum.hibernate.org/viewtopic.php?t=941520, but was wondering if we could just patch the registerReverseHibernateTypeMappings() in org.hibernate.dialect.Oracle9iDialect to resolve this? Adding the following line seems to fix this: registerHibernateType(-101, "timestamp"); If necessary, I can submit this as a patch... -- 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

18 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2008