March 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-613) search by criteria with sub-class Example do not bind sub-class properties

by Paul Benedict (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-613?page=co... ] Paul Benedict commented on HHH-613: ----------------------------------- I'd like to know why this is correct behavior. I also am trying to perform sub-criteria on a polymorphic association. I really am looking for a particular type, and I have not read anywhere -- at least from what I can find -- why this isn't supported. Is it a technical limitation? A philosophical limitation? Time constraint? > search by criteria with sub-class Example do not bind sub-class properties > -------------------------------------------------------------------------- > > Key: HHH-613 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-613 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Reporter: Foaloke > Priority: Blocker > > class Animal { > private Int age; > ... > } > class Pet extends Animal { > private String name; > ... > } > Pet pet = new Pet(); > pet.setName("Fritz"); > session.createCriteria(Animal.class).add(Example.create(pet)).list(); > This will simply return all 'Pets', no binding occurs with the "name" property of Pet. > This could, more probably, occurs if I have some Country which contains Animals & I want to look for some kind of Pets in that country : > session.createCriteria(Country.class).createCriteria("animal").add(Example.create(pet)).list(); -- 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-3175) Could not locate TransactionManager in OAS middle Tier

by purandhar P (JIRA)

Could not locate TransactionManager in OAS middle Tier ------------------------------------------------------ Key: HHH-3175 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3175 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Oracle Application Server 10.1.2 middle tier with portal and infrastructure services Reporter: purandhar P my hibernate.cfg.xml files is like this <property name="connection.datasource">jdbc/RMDBConnectionPooledDS</property> <property name="transaction.manager_lookup_class">org.hibernate.transaction.OC4JTransactionManagerLookup</property> <property name="transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property> <property name="FlushBeforeCompletionEnabled">true</property> <property name="AutoCloseSessionEnabled">true</property> <property name="jndi.url">opmn:ormi://localhost:80/RM_Application</property> <property name="jndi.class">com.evermind.server.rmi.RMIInitialContextFactory</property> <property name="jndi.security.principal">jazn.com/admin</property> <property name="jndi.security.credentials">password1</property> <property name="dedicated.rmicontext">true</property> <property name="dedicated.connection">true</property> <property name="jta.UserTransaction">java:comp/UserTransaction</property> <property name="current_session_context_class">jta</property> <property name="jdbc.batch_size">200</property> <property name="autocommit">false</property> <property name="autoRollback">true</property> org.hibernate.HibernateException: Could not locate TransactionManager at org.hibernate.transaction.JNDITransactionManagerLookup.getTransactionManager(JNDITransactionManagerLookup.java:26) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:325) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) at com.osg.rmp.dao.util.HibernateFactory.configureSessionFactory(Unknown Source) at com.osg.rmp.dao.util.HibernateFactory.buildIfNeeded(Unknown Source) at com.osg.rmp.dao.util.HibernateFactory.openSession(Unknown Source) at com.osg.rmp.dao.MasterDataDAO.getImpactUnitsList(Unknown Source) at com.osg.rmp.ajax.util.RMData.<clinit>(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:219) at com.osg.rmp.ajax.servlet.RMContextListener.contextInitialized(RMContextListener.java:43) at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1009) at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:549) at com.evermind.server.Application.getHttpApplication(Application.java:890) at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:707) at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:625) at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:278) at com.evermind.server.http.HttpServer.setSites(HttpServer.java:278) at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:179) at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2394) at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1551) at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92) at java.lang.Thread.run(Thread.java:534) Caused by: javax.naming.NameNotFoundException: No object bound for java:comp/pm/TransactionManager at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.hibernate.transaction.JNDITransactionManagerLookup.getTransactionManager(JNDITransactionManagerLookup.java:23) -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-171) Do not log missing objects when using QueryLoader

by Emmanuel Bernard (JIRA)

Do not log missing objects when using QueryLoader ------------------------------------------------- Key: HSEARCH-171 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-171 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.1.GA Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.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
1
0 / 0

[Hibernate-JIRA] Created: (ANN-710) MapKeyManyToMany name attribute gets ignored

by James Roper (JIRA)

MapKeyManyToMany name attribute gets ignored -------------------------------------------- Key: ANN-710 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-710 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.5 PostgreSQL dialect Reporter: James Roper The following mapping: @CollectionOfElements @JoinTable(name = "my_join_table", joinColumns = @JoinColumn(name = "my_id")) @Column(name = "text") @Enumerated(EnumType.STRING) @MapKeyManyToMany(joinColumns = @JoinColumn(name = "my_enum")) private Map<MyEnum, String> text; Generates the following table: create table my_join_table ( my_id int8 not null, text varchar(255), mapkey varchar(255), primary key (my_id, mapkey) ); So, the "my_enum" column name is ignored, and "mapkey" is used instead. Note that the key for the map is an enum. Also, I don't see any way to set the length of a mapped column for String mapped enums. -- 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 month

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy

by Peter Lupo (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c... ] Peter Lupo commented on HHH-1657: --------------------------------- The hardest has been done. The issue has been localized in the code. Even a patch was proposed. If it is accepted, the fix is instantaneous. I don't have the necessary knowledge to evaluate the patch or the permissions to apply it, so I guess I can't do anything. As the patch is already available, I think the assignee won't be stuck for a very long time on this issue. Even if the patch is not ok, the issue has already been found in the code. Isn't there anyone available for this bug to be assigned to? It will be a very short time spent to address a critical bug out! > hql update generate wrong sql with joined subclass hierarcy > ----------------------------------------------------------- > > Key: HHH-1657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657 > Project: Hibernate3 > Issue Type: Bug > Components: query-hql > Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3 > Reporter: Alexey Romanchuk > Priority: Critical > > Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method. > When I try to update Child by id with hql: > update Child c set c.field = 'value' where c.id = 1234 > hibernate generates joined tables like > insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234 > look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous -- 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 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3185) Implement en optimistic Repeatable Read lock mode

by Emmanuel Bernard (JIRA)

Implement en optimistic Repeatable Read lock mode ------------------------------------------------- Key: HHH-3185 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3185 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Emmanuel Bernard Wrt JPA's LockModeType.READ (and WRITE). There could be implemented as "check the version at the end of the transaction" even for locked entities that have not been modified. The current Hibernate optimistic lock only check the version of updated entities and was not suitable to be mapped on LockModeType.READ -- 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 month

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-324) Deployed Maven POM incorrectly excludes transitive dependency

by Joe Germuska (JIRA)

Deployed Maven POM incorrectly excludes transitive dependency ------------------------------------------------------------- Key: EJB-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-324 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Maven 2 Reporter: Joe Germuska Priority: Trivial The deployed Maven POM for Hibernate Entity Manager 3.3.1.ga incorrectly excludes the dependency upon the oswego-concurrent libraries (see below). This leads to a NoClassDefFound error: nested exception is java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap Caused by: java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap at org.jboss.util.file.ArchiveBrowser.<clinit>(ArchiveBrowser.java:52) I haven't yet determined how the Maven POMs are being managed by the Hibernate team, but they don't seem to be in Subversion; therefore, I've marked this trivial, although it is a little more than that for someone who is trying to use the Maven repository. In any case, it should be easy to fix. More generally, it might be more correct to employ Maven's ranged version dependency syntax, instead of explicitly excluding other dependencies. excerpt from http://repo1.maven.org/maven2/org/hibernate/hibernate-entitymanager/3.3.1... <dependency> <groupId>jboss</groupId> <artifactId>jboss-common-core</artifactId> <version>2.0.4.GA</version> <exclusions> ... <exclusion> <groupId>oswego-concurrent</groupId> <artifactId>concurrent</artifactId> </exclusion> ... </exclusions> </dependency> -- 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 month

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3178) Disappearing values for a managed Map

by Peter Aarestad (JIRA)

Disappearing values for a managed Map ------------------------------------- Key: HHH-3178 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3178 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, Microsoft SQL Server 2005 Reporter: Peter Aarestad My mapping looks like this (obfuscated but functionally equivalent): {code} <hibernate-mapping package="foo.bar.blah"> <class name="PaperTypes" table="PaperTypes" lazy="false"> <id name="paperTypeId" column="paperTypeID"> <generator class="native" /> </id>  <map name="weightsAvailable" table="PaperWeightsAvailable" inverse="true" lazy="false" cascade="all-delete-orphan"> <key column="fk_paperTypeID" /> <map-key-many-to-many class="PaperWeight" column="fk_paperWeightID" /> <one-to-many class="PaperWeightsAvailable" /> </map> </class> </hibernate-mapping> {code} For at least one version of the PaperTypes object, I'm getting an issue where, when you examine the "weightsAvailable" Map, you see that it is paired correctly with a PaperWeightsAvailable object, but get() comes back null. So this code dies: {code} // 'map' is the Hibernate map Map<Integer, Set<Integer>> deflated = new Hashtable<Integer, Set<Integer>>(); Set<PaperWeight> keys = new TreeSet<PaperWeight>(workingMap.keySet()); for (PaperWeight pw : keys) { Set<Integer> set = new TreeSet<Integer>(); // This is where it dies: workingMap.get(pw) should NEVER come back null, but it does sometimes... for (PaperSizes ps : workingMap.get(pw).getSizesAvailable()) { set.add(ps.getPaperSizeId()); } deflated.put(pw.getPaperWeightId(), set); } {code} I worked around this bug by creating a new HashMap based on the Hibernate map: {code} Map<PaperWeight, PaperWeightsAvailable> workingMap = new HashMap<PaperWeight, PaperWeightsAvailable>(map); {code} but that should not be necssarily obviouisly. -- 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 month

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c... ] Gail Badner commented on HHH-1657: ---------------------------------- A patch is attached to HHH-3150. > hql update generate wrong sql with joined subclass hierarcy > ----------------------------------------------------------- > > Key: HHH-1657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657 > Project: Hibernate3 > Issue Type: Bug > Components: query-hql > Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3 > Reporter: Alexey Romanchuk > Priority: Critical > > Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method. > When I try to update Child by id with hql: > update Child c set c.field = 'value' where c.id = 1234 > hibernate generates joined tables like > insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234 > look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous -- 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 month

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-607) The source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution.

by Steve Gilbert (JIRA)

The source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution. ------------------------------------------------------------------------------------------- Key: ANN-607 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-607 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.3. Reporter: Steve Gilbert As noted in the summary, the source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution. -- 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 month

3
8
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