November 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-1098) Seam skeleton app exporter is not visible

by Ali (JIRA)

Seam skeleton app exporter is not visible ----------------------------------------- Key: HBX-1098 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1098 Project: Hibernate Tools Issue Type: New Feature Components: reverse-engineer Reporter: Ali Priority: Critical i use eclipse europa and the latest hibernate tools integrated with each other. How can i make the seam skeleton app exporter visible?? please help me.. or can you give me link of an eclipse bundle including seam skeleton app exporter which i can download? -- 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

16 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-309) PurgeAllLuceneWork duplicates in work queue

by Sanne Grinovero (JIRA)

PurgeAllLuceneWork duplicates in work queue ------------------------------------------- Key: HSEARCH-309 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-309 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.CR1 Reporter: Sanne Grinovero Fix For: 3.1.0 when using purgeAll( typeA ); you get two works to purge typeA in the queue, +1 for each subclass. The problem is caused by the presence of each type in the set of it's subtypes in DocumentBuilderContainedEntity.subclasses I tried having the typeA removed from the subclasses set, but this breaks many other features (junit told). It appears some other code is relying on the fact that this set has to contain the super class too; this looks strange? so the easy fix would be to change the current purgeAll() to not purge on the root entity too, as doing it on subclasses is enough; but it actually feels to me this is the only correct method, and we should check other usages. I've seen this affect only purgeAll but could be more critical, so priority must be investigated. -- 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

16 years, 1 month

2
8
0 / 0

[Hibernate-JIRA] Created: (ANN-788) Missing sensible default for @Table.appliesTo

by Matjaz Smolej (JIRA)

Missing sensible default for @Table.appliesTo --------------------------------------------- Key: ANN-788 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-788 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.4.0.GA Reporter: Matjaz Smolej appliesTo attribute in @org.hibernate.annotations.Table is mandatory even for primary table. Default empty string could indicate explicit, implicit or naming strategy provided primary table name. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1015) Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table

by Krasimir Chobantonov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015?page=c... ] Krasimir Chobantonov commented on HHH-1015: ------------------------------------------- Once the http://opensource.atlassian.com/projects/hibernate/browse/HHH-1001 is fixed then we can change the patch to properly find the reverse side instead of relaying on the column names. > Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table > ----------------------------------------------------------------------------------------- > > Key: HHH-1015 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 beta 2 > Environment: Hibernate versions 3.1 beta 3 and 3.0.5 > Reporter: Steven Grimm > Priority: Minor > Attachments: hhh-1015.patch > > > I have the following mappings describing a hierarchy of events and a class that the events refer to: > <hibernate-mapping package="com.xyz"> > <class name="Event" table="event" discriminator-value="-1"> > <id name="Id" type="long" column="event_id"/> > <discriminator column="event_type_id" type="integer" /> > <subclass name="EventPayer" discriminator-value="-3"> > <join table="event_payer"> > <key column="event_id" /> > <many-to-one name="payer" column="payer_id" class="Payer" /> > </join> > <subclass name="EventPayerCreated" discriminator-value="1" /> > </subclass> > </class> > <class name="Payer" table="payer"> > <id name="payerId" column="payer_id" type="java.lang.Long"/> > <set name="eventPayers" inverse="true" cascade="save-update"> > <key column="payer_id"/> > <one-to-many class="EventPayer"/> > </set> > </class> > </hibernate-mapping> > When I fetch the Payer.eventPayers collection, Hibernate generates this SQL: > select eventpayer0_.payer_id as payer7_1_, > eventpayer0_.event_id as event1_1_, > eventpayer0_.event_id as event1_5_0_, > eventpayer0_1_.payer_id as payer2_6_0_, > eventpayer0_.event_type_id as event2_5_0_ > from event eventpayer0_ > inner join event_payer eventpayer0_1_ > on eventpayer0_.event_id=eventpayer0_1_.event_id > where eventpayer0_.payer_id=? > The problem is that there is no event.payer_id column; payer_id is in the child table, not the parent. It appears that specifying a discriminated subclass in <one-to-many> is the same as specifying the superclass, or that Hibernate is ignoring the subclass's <join> element. As far as I can tell, this leaves no way to resolve bidirectional associations where one end of the association is in a discriminated subclass, which seems like a perfectly reasonable thing to want to do. > I also tried changing <key column="payer_id"/> to <key property-ref="payer"/> in the Payer class's <set> element, but got similar behavior in the form of a "property not found" error: Hibernate is either looking in the superclass's properties rather than the subclass's or is ignoring the list of properties in the <join> element. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1015) Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table

by Krasimir Chobantonov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015?page=c... ] Krasimir Chobantonov updated HHH-1015: -------------------------------------- Attachment: hhh-1015.patch Attaching a patch that fixes the problem - the patch is against Hibernate core version 3.3.1.GA. Note that because hibernate does not keep the reverse property to the OneToMany relationships when using HBM (e.g. key element does have only the column information) then the path relies only on the column name information to get to the reverse property and to check if it is mapped to a join table (e.g. using SecondaryTable annotation) Also the code is only modified so that the described case in the issue is going to work and also fixes the problem with the Hibernate schema validation. Probably there may be some other places that needs to be fixed as well (this needs to be validated byt the respective components' owners) > Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table > ----------------------------------------------------------------------------------------- > > Key: HHH-1015 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 beta 2 > Environment: Hibernate versions 3.1 beta 3 and 3.0.5 > Reporter: Steven Grimm > Priority: Minor > Attachments: hhh-1015.patch > > > I have the following mappings describing a hierarchy of events and a class that the events refer to: > <hibernate-mapping package="com.xyz"> > <class name="Event" table="event" discriminator-value="-1"> > <id name="Id" type="long" column="event_id"/> > <discriminator column="event_type_id" type="integer" /> > <subclass name="EventPayer" discriminator-value="-3"> > <join table="event_payer"> > <key column="event_id" /> > <many-to-one name="payer" column="payer_id" class="Payer" /> > </join> > <subclass name="EventPayerCreated" discriminator-value="1" /> > </subclass> > </class> > <class name="Payer" table="payer"> > <id name="payerId" column="payer_id" type="java.lang.Long"/> > <set name="eventPayers" inverse="true" cascade="save-update"> > <key column="payer_id"/> > <one-to-many class="EventPayer"/> > </set> > </class> > </hibernate-mapping> > When I fetch the Payer.eventPayers collection, Hibernate generates this SQL: > select eventpayer0_.payer_id as payer7_1_, > eventpayer0_.event_id as event1_1_, > eventpayer0_.event_id as event1_5_0_, > eventpayer0_1_.payer_id as payer2_6_0_, > eventpayer0_.event_type_id as event2_5_0_ > from event eventpayer0_ > inner join event_payer eventpayer0_1_ > on eventpayer0_.event_id=eventpayer0_1_.event_id > where eventpayer0_.payer_id=? > The problem is that there is no event.payer_id column; payer_id is in the child table, not the parent. It appears that specifying a discriminated subclass in <one-to-many> is the same as specifying the superclass, or that Hibernate is ignoring the subclass's <join> element. As far as I can tell, this leaves no way to resolve bidirectional associations where one end of the association is in a discriminated subclass, which seems like a perfectly reasonable thing to want to do. > I also tried changing <key column="payer_id"/> to <key property-ref="payer"/> in the Payer class's <set> element, but got similar behavior in the form of a "property not found" error: Hibernate is either looking in the superclass's properties rather than the subclass's or is ignoring the list of properties in the <join> element. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-268) Run optimize() (all classes) in parallel

by Emmanuel Bernard (JIRA)

Run optimize() (all classes) in parallel ---------------------------------------- Key: HSEARCH-268 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-268 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Assignee: Sanne Grinovero Fix For: 3.1.0 Sanne I am assigning this to you. It seems the work in // could be done with your refactoring instead of locally. -- 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

16 years, 1 month

2
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-311) Add a close() method to BackendQueueProcessorFactory

by Sanne Grinovero (JIRA)

Add a close() method to BackendQueueProcessorFactory ---------------------------------------------------- Key: HSEARCH-311 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-311 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero 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

16 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3626) include the eclipse:eclipse plugin in parent/pom.xml file in the pluginManagement section so that hibernate project can use - mvn eclipse:eclipse to generated the eclipse project artifacts.

by Krasimir Chobantonov (JIRA)

include the eclipse:eclipse plugin in parent/pom.xml file in the pluginManagement section so that hibernate project can use - mvn eclipse:eclipse to generated the eclipse project artifacts. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3626 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3626 Project: Hibernate Core Issue Type: Improvement Components: build Affects Versions: 3.3.1 Reporter: Krasimir Chobantonov here is the plugin section inside the pluginManagement element <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-eclipse-plugin</artifactId> <version>2.5</version> </plugin> -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3625) Add JBoss repository in the parent/pom.xml file

by Krasimir Chobantonov (JIRA)

Add JBoss repository in the parent/pom.xml file ----------------------------------------------- Key: HHH-3625 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3625 Project: Hibernate Core Issue Type: Improvement Components: build Affects Versions: 3.3.1 Reporter: Krasimir Chobantonov the following xml snipped may be used in the parent/pom.xml file so that the JBoss repository will be know by maven <repositories> <repository> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> <id>jboss</id> <name>jboss</name> <url>http://repository.jboss.org/maven2</url> </repository> </repositories> <pluginRepositories> <pluginRepository> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> <id>jboss</id> <name>jboss</name> <url>http://repository.jboss.org/maven2</url> </pluginRepository> </pluginRepositories> -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1015) Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table

by Krasimir Chobantonov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015?page=c... ] Krasimir Chobantonov commented on HHH-1015: ------------------------------------------- http://opensource.atlassian.com/projects/hibernate/browse/HHH-1001 is related to this issue - the reason is that the currently the only meta data that we can rely on to get the oposite side of the relationship is based on the column name > Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table > ----------------------------------------------------------------------------------------- > > Key: HHH-1015 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 beta 2 > Environment: Hibernate versions 3.1 beta 3 and 3.0.5 > Reporter: Steven Grimm > Priority: Minor > > I have the following mappings describing a hierarchy of events and a class that the events refer to: > <hibernate-mapping package="com.xyz"> > <class name="Event" table="event" discriminator-value="-1"> > <id name="Id" type="long" column="event_id"/> > <discriminator column="event_type_id" type="integer" /> > <subclass name="EventPayer" discriminator-value="-3"> > <join table="event_payer"> > <key column="event_id" /> > <many-to-one name="payer" column="payer_id" class="Payer" /> > </join> > <subclass name="EventPayerCreated" discriminator-value="1" /> > </subclass> > </class> > <class name="Payer" table="payer"> > <id name="payerId" column="payer_id" type="java.lang.Long"/> > <set name="eventPayers" inverse="true" cascade="save-update"> > <key column="payer_id"/> > <one-to-many class="EventPayer"/> > </set> > </class> > </hibernate-mapping> > When I fetch the Payer.eventPayers collection, Hibernate generates this SQL: > select eventpayer0_.payer_id as payer7_1_, > eventpayer0_.event_id as event1_1_, > eventpayer0_.event_id as event1_5_0_, > eventpayer0_1_.payer_id as payer2_6_0_, > eventpayer0_.event_type_id as event2_5_0_ > from event eventpayer0_ > inner join event_payer eventpayer0_1_ > on eventpayer0_.event_id=eventpayer0_1_.event_id > where eventpayer0_.payer_id=? > The problem is that there is no event.payer_id column; payer_id is in the child table, not the parent. It appears that specifying a discriminated subclass in <one-to-many> is the same as specifying the superclass, or that Hibernate is ignoring the subclass's <join> element. As far as I can tell, this leaves no way to resolve bidirectional associations where one end of the association is in a discriminated subclass, which seems like a perfectly reasonable thing to want to do. > I also tried changing <key column="payer_id"/> to <key property-ref="payer"/> in the Payer class's <set> element, but got similar behavior in the form of a "property not found" error: Hibernate is either looking in the superclass's properties rather than the subclass's or is ignoring the list of properties in the <join> element. -- 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

16 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2008