August 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-1980) disallow the mapping combination of <version/> and optimistic-lock

by Steve Ebersole (JIRA)

disallow the mapping combination of <version/> and optimistic-lock ------------------------------------------------------------------ Key: HHH-1980 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1980 Project: Hibernate3 Type: Improvement Components: core Reporter: Steve Ebersole Assigned to: Steve Ebersole Priority: Minor Fix For: 3.2.0.ga After fixing HHH-1677, some tests started to fail. The reason they fail is that the code used to fix it assumes that either a version/timestamp is used or optimistic-lock is used but that these two options are mutually exclusive. However, that is currently not the case as this combination is not validated against. These two settings obviously do not make sense together. -- 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, 5 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (ANN-381) Make possible to specify an @EmbeddedId's field in a @OneToMany's mappedBy property

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-381?page=co... ] Emmanuel Bernard commented on ANN-381: -------------------------------------- John, a patch is very welcome :-) > Make possible to specify an @EmbeddedId's field in a @OneToMany's mappedBy property > ----------------------------------------------------------------------------------- > > Key: ANN-381 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-381 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Environment: Hibernate's annotations packaged in JBoss EJB 3.0 RC8- FD > Microsoft SQL Server 2000 > Reporter: Pierre Fourès > Fix For: 3.2.0 > > > As described in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=960763) and discussed with Emmanuel, it would be very nice to be able to specify in an @OneToMany's mappedBy property the field of an @EmbeddedId. > For example, i would like to be able run this example : > @Entity > public class Card { > @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER, mappedBy="primaryKey.card") > private Set<CardField> fields; > } > @Entity > public class CardField implements Field { > @EmbeddedId > private PrimaryKey primaryKey = new PrimaryKey(); > > @Embeddable > class PrimaryKey implements Serializable { > @ManyToOne(optional = false) > private Card card; > > @ManyToOne(optional = false) > private Key key; > } > } > @Entity > public class Key {} -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-713) hbm2java task: meta support needed for class level annotations

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-713?page=co... ] Max Rydahl Andersen commented on HBX-713: ----------------------------------------- I were only arguing that why would you ever have both hbm.xml and entity annotations for the same class at the same time ? generating seam annotations or other annotations than entity-annotations might make sense yes. > hbm2java task: meta support needed for class level annotations > -------------------------------------------------------------- > > Key: HBX-713 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-713 > Project: Hibernate Tools > Type: Bug > Components: hbm2java > Versions: 3.2beta6 > Environment: hibernate tools 3.2 beta 6 > JBoss 4.0.4.GA with EJB3 > Reporter: Daniel Pocock > > Original Estimate: 1 hour > Remaining: 1 hour > > We use hbm2java to create EJB3 entity beans from hbm files. It would be really useful to use the `meta' element to insert additional class level annotations. Is someone already working on such a feature, or should I submit a patch? > Here is an example of what I would like to do: > <meta attribute="extra-import">org.jboss.seam.annotations.Name</meta> > <meta attributre="class-annotation">@Name("myObject")</meta> > such that the following code would be generated: > import javax.ejb.Entity; > import org.jboss.seam.annotations.Name; > @Entity > @Name("myObject") > public class MyObject .... -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-713) hbm2java task: meta support needed for class level annotations

by Daniel Pocock (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-713?page=co... ] Daniel Pocock commented on HBX-713: ----------------------------------- Can you point me to an example? I assume you are suggesting that I should write entity bean classes by hand, but I am trying to avoid that, as writing a hbm.xml is quicker and leaves less possibilities for error. Is there any reason why the meta attribute I have proposed shouldn't be included in Hibernate tools? Would you be happy if I submitted a patch to provide this feature? > hbm2java task: meta support needed for class level annotations > -------------------------------------------------------------- > > Key: HBX-713 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-713 > Project: Hibernate Tools > Type: Bug > Components: hbm2java > Versions: 3.2beta6 > Environment: hibernate tools 3.2 beta 6 > JBoss 4.0.4.GA with EJB3 > Reporter: Daniel Pocock > > Original Estimate: 1 hour > Remaining: 1 hour > > We use hbm2java to create EJB3 entity beans from hbm files. It would be really useful to use the `meta' element to insert additional class level annotations. Is someone already working on such a feature, or should I submit a patch? > Here is an example of what I would like to do: > <meta attribute="extra-import">org.jboss.seam.annotations.Name</meta> > <meta attributre="class-annotation">@Name("myObject")</meta> > such that the following code would be generated: > import javax.ejb.Entity; > import org.jboss.seam.annotations.Name; > @Entity > @Name("myObject") > public class MyObject .... -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-381) Make possible to specify an @EmbeddedId's field in a @OneToMany's mappedBy property

by John Schneider (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-381?page=co... ] John Schneider commented on ANN-381: ------------------------------------ I strugled with this problem for hours before I found this post. The workaround of creating delegate getters and setters for composite key fields is ugly. > Make possible to specify an @EmbeddedId's field in a @OneToMany's mappedBy property > ----------------------------------------------------------------------------------- > > Key: ANN-381 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-381 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Environment: Hibernate's annotations packaged in JBoss EJB 3.0 RC8- FD > Microsoft SQL Server 2000 > Reporter: Pierre Fourès > Fix For: 3.2.0 > > > As described in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=960763) and discussed with Emmanuel, it would be very nice to be able to specify in an @OneToMany's mappedBy property the field of an @EmbeddedId. > For example, i would like to be able run this example : > @Entity > public class Card { > @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER, mappedBy="primaryKey.card") > private Set<CardField> fields; > } > @Entity > public class CardField implements Field { > @EmbeddedId > private PrimaryKey primaryKey = new PrimaryKey(); > > @Embeddable > class PrimaryKey implements Serializable { > @ManyToOne(optional = false) > private Card card; > > @ManyToOne(optional = false) > private Key key; > } > } > @Entity > public class Key {} -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-209) Compositekey find and delete does not work

by Rakesh Gupta (JIRA)

Compositekey find and delete does not work ------------------------------------------ Key: EJB-209 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-209 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.cr1 Environment: hibernate core 3.2.0cr2, hibernate-annotation 3.2.0.cr1, hibernate-entitymanager3.2.0.cr1 Reporter: Rakesh Gupta Priority: Blocker First I am using ejb3 annotation and no XML mapping files and generated the code using jboss-eclipse IDE I have two tables table A and Table B, Table A has single primarykey but table B has only two fields and combination of both is the primarykey also out of these two fields one has references to table A and other has a reference to some other table. Problem; I seach a records in table A using single primary key, based on this i gets all the records of table B in a collection, and when i try to delete a records from table be it is not deleted. I I try to remove this from the collection and then persist it does not work. there after i try to delete directly from table B but this also does not work. even composite key search like entitymanager.find(A.class, compositekey) is also not working. please let me know if this is a bug or some problem -- 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, 5 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1974) create area in svn for translation of hibernate reference for the Portuguese of Brazil

by Marvin Herman Froeder (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1974?page=c... ] Marvin Herman Froeder commented on HHH-1974: -------------------------------------------- I still in. VELO > create area in svn for translation of hibernate reference for the Portuguese of Brazil > -------------------------------------------------------------------------------------- > > Key: HHH-1974 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1974 > Project: Hibernate3 > Type: Improvement > Components: documentation > Environment: Hibernate 3.x > Reporter: mauricio gamarra > Assignee: Steve Ebersole > Attachments: hibernate_reference.zip, pt_br.zip > > > I am part of a group of people that made the translation of hibernate reference for the Portuguese .Brazil . > I would like to know as we can be including this translation in the distribution of hibernate. > The translation already this in the format xml of docbock and this being maked in ant. > I made dowload of hibernate in svn and used the documentation in English as model for the translation for the Portuguese. > The almost complete work already this, lacking only 4 chapters. > We have worked intensely to conclude them the possible fastest work. > Please they pass me instructions of as to be placing the archives in svn > I am sent xml and the pdf for your analyzes -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1278) It seems that LockAcquisitionException is never thrown out.

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278?page=all ] Steve Ebersole closed HHH-1278: ------------------------------- Resolution: Rejected > It seems that LockAcquisitionException is never thrown out. > ----------------------------------------------------------- > > Key: HHH-1278 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Environment: Win, Hibernate3.1, Oracle10G > Reporter: Dongsheng Wang > > > I used to catch LockAcquisitionException to decide if I got the lock. It works. After I update hibernate from 3.0 to 3.1. It seems that LockAcquisitionException is never thrown out. Instead, an JDBCException is thrown out. I checked the source, it seems that the LockAcquisitionException's constructor is never called by anybody. > Is it a bug or something? -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Reopened: (HHH-1278) It seems that LockAcquisitionException is never thrown out.

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278?page=all ] Steve Ebersole reopened HHH-1278: --------------------------------- > It seems that LockAcquisitionException is never thrown out. > ----------------------------------------------------------- > > Key: HHH-1278 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Environment: Win, Hibernate3.1, Oracle10G > Reporter: Dongsheng Wang > > > I used to catch LockAcquisitionException to decide if I got the lock. It works. After I update hibernate from 3.0 to 3.1. It seems that LockAcquisitionException is never thrown out. Instead, an JDBCException is thrown out. I checked the source, it seems that the LockAcquisitionException's constructor is never called by anybody. > Is it a bug or something? -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1278) It seems that LockAcquisitionException is never thrown out.

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278?page=all ] Steve Ebersole closed HHH-1278: ------------------------------- Resolution: Fixed Nope. We actually ripped out all the code that used to interpret the vendor specific error codes because that stuff is a nightmare to maintain. The core Hibernate code only ever uses the X/Open SQLState codes now to decipher the type of exception. Unfortunately, there is not a standard X/Open SQLState code relating to lock acquisition errors. If it is that important, just plugin in a custom SQLExceptionConverter and convert check your db vendor's specific lock acquisition issue error codes. > It seems that LockAcquisitionException is never thrown out. > ----------------------------------------------------------- > > Key: HHH-1278 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1278 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Environment: Win, Hibernate3.1, Oracle10G > Reporter: Dongsheng Wang > > > I used to catch LockAcquisitionException to decide if I got the lock. It works. After I update hibernate from 3.0 to 3.1. It seems that LockAcquisitionException is never thrown out. Instead, an JDBCException is thrown out. I checked the source, it seems that the LockAcquisitionException's constructor is never called by anybody. > Is it a bug or something? -- 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, 5 months

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 August 2006