February 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-339) Duplicate Loading of META-INF/orm.xml if specified in perstistence.xml

by Mirko Novakovic (JIRA)

Duplicate Loading of META-INF/orm.xml if specified in perstistence.xml ---------------------------------------------------------------------- Key: EJB-339 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-339 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: JBoss 4.2.2.GA Sun Java 6 Reporter: Mirko Novakovic Priority: Minor I had specified <mapping-file>/META-INF/orm.xml</mapping-file> in my persistence.xml to load the standard orm.xml, which included some named queries. When deploying and starting the application in JBoss, I get the following exception: org.hibernate.DuplicateMappingException: Duplicate query mapping After removing the <mapping-file>/META-INF/orm.xml</mapping-file> from my perstistence.xml, the application works fine. It seems that the EntityManager loads the default META-INF/orm.xml and the one specified in the persistence.xml, even if they are the same. This is not a big issue, but took me some time to find it out and I think it would be better to log a warning in this case or just ignore duplications. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-697) @Transient property leads to org.hibernate.AnnotationException: Property has an unbound type

by Sebastian Baltes (JIRA)

@Transient property leads to org.hibernate.AnnotationException: Property has an unbound type --------------------------------------------------------------------------------------------- Key: ANN-697 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-697 Project: Hibernate Annotations Issue Type: Bug Reporter: Sebastian Baltes -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-442) Support @GenericGenerators

by Emmanuel Bernard (JIRA)

Support @GenericGenerators -------------------------- Key: ANN-442 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-442 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Emmanuel Bernard Priority: Minor To support more than one generic generator in package-info.java -- 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, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3120) Linter Dialect for Hibernate 3

by Galina Ermakova (JIRA)

Linter Dialect for Hibernate 3 ------------------------------ Key: HHH-3120 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3120 Project: Hibernate3 Issue Type: New Feature Affects Versions: 3.2.x, 3.3, 3.4 Environment: Hibernate 3.x version Reporter: Galina Ermakova Attachments: LinterDialect.java I have written a Linter Dialect for Hibernate 3 that I would like to contribute with. The LinterDialect that makes it possible to work with Linter RDBMS. (http://www.linter.ru/en/main) -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-129) IndexedEmbedded for Collections Documentation

by Jay Bose (JIRA)

IndexedEmbedded for Collections Documentation --------------------------------------------- Key: HSEARCH-129 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-129 Project: Hibernate Search Issue Type: Improvement Reporter: Jay Bose I was wondering why a query like "parent.child.name:foo" was not working. After a few different searches I found this response -- http://forum.hibernate.org/viewtopic.php?p=2348475#2348475 It would be helpful if the current documentation described if and how associated objects (collections) should be indexed for certain queries. Also, should @ContainedIn AND @IndexedEmbedded be used for one collection? See below. @ContainedIn @IndexedEmbedded(depth = 1) Set<Keyword> keywords; -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3118) order by with sub-select

by Magnus Sandberg (JIRA)

order by with sub-select ------------------------ Key: HHH-3118 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3118 Project: Hibernate3 Issue Type: Improvement Components: query-hql Affects Versions: 3.2.3 Reporter: Magnus Sandberg I'd like to order by a column that is created with a sub-select: select a.b, (select c from [...]) from [...] where [...]; naming the sub-select column does not work: select a.b, (select c from [...]) as to_order from [...] where [...] order by to_order; gives a "no such column" exception. I think hql should accept order by from named columns. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3117) Proposal for better (more speaking) Exceptions

by Daniel Migowski (JIRA)

Proposal for better (more speaking) Exceptions ---------------------------------------------- Key: HHH-3117 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3117 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Reporter: Daniel Migowski Priority: Minor Currently I get LazyInitializationExceptions in my Logfiles. To debug them, it would be great to know from with lazy objects they originate. To achive this I currently override the AbstractLazyInitializer class and add the entityName and Id to the ExceptionText. The modified source is like this (Just the exception messages have been modified): public final void initialize() throws HibernateException { if (!initialized) { if ( session==null ) { throw new LazyInitializationException("could not initialize proxy for "+entityName+"("+id+") - no Session"); } else if ( !session.isOpen() ) { throw new LazyInitializationException("could not initialize proxy for "+entityName+"("+id+") - the owning Session was closed"); } else if ( !session.isConnected() ) { throw new LazyInitializationException("could not initialize proxy for "+entityName+"("+id+") - the owning Session is disconnected"); } else { target = session.immediateLoad(entityName, id); initialized = true; checkTargetState(); } } else { checkTargetState(); } } private void checkTargetState() { if ( !unwrap ) { if ( target == null ) { getSession().getFactory().getEntityNotFoundDelegate().handleEntityNotFound( entityName, id ); } } } public final void setSession(SessionImplementor s) throws HibernateException { if (s!=session) { if ( isConnectedToSession() ) { //TODO: perhaps this should be some other RuntimeException... throw new HibernateException("illegally attempted to associate a proxy for "+entityName+"("+id+") with two open Sessions"); } session = s; } } -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-140) Discriminator column not supported with JOINED strategy

by Pavel (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-140?page=co... ] Pavel commented on ANN-140: ---------------------------- It would be nice to see how the problem with the multiple joins is faced when the underlying DB has restriction on the number of joins one can execute in a single SQL? For instance MySQL seems to allow only 31 joins. What happens if the class hierarchy has more than 31 sub-classes? > Discriminator column not supported with JOINED strategy > ------------------------------------------------------- > > Key: ANN-140 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-140 > Project: Hibernate Annotations > Issue Type: Bug > Affects Versions: 3.1beta6 > Environment: Hibernate 3.1rc2, Hibernate Annotations 3.1b6 > Reporter: Steven Grimm > > Section 9.1.27 of the EJB3 persistence public draft says, "The DiscriminatorColumn annotation is used to define the discriminator column for SINGLE_TABLE and JOINED mapping strategies." But Hibernate ignores the DiscriminatorColumn annotation when the mapping strategy is JOINED; when a JOINED entity is persisted, its discriminator column is not included in the SQL "insert" statement, resulting in a not-null constraint violation if the discriminator column is marked NOT NULL in the database. > The JOINED strategy with discriminators is pretty ubiquitous in EJB3 sample code and tutorials out on the net, so lots of people are likely to run into this as they try out EJB3 for the first time. A few examples: > http://www.oracle.com/technology/tech/java/oc4j/ejb3/howtos-ejb3/howtoejb... > http://www.solarmetric.com/Software/Documentation/4.0.0EA/docs/full/html/... > http://www.caucho.com/resin-3.0/amber/tutorial/cmp-inherit/index.xtp -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3116) OpenEJBTransactionManagerLookup

by David Blevins (JIRA)

OpenEJBTransactionManagerLookup ------------------------------- Key: HHH-3116 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3116 Project: Hibernate3 Issue Type: Patch Components: core Reporter: David Blevins Attachments: OPENEJB-TX-MANAGER.patch One for the collection. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3115) org.hibernate.HibernateException: CGLIB Enhancement failed -- is terribly uninformative exception

by John Towell (JIRA)

org.hibernate.HibernateException: CGLIB Enhancement failed -- is terribly uninformative exception -------------------------------------------------------------------------------------------------- Key: HHH-3115 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3115 Project: Hibernate3 Issue Type: Improvement Environment: any hibernate any DB Reporter: John Towell I have had hibernate through this exception several times and have no idea why until I googled the exception and found the faq that says. http://www.hibernate.org/116.html#A5 "If you use lazy loading with proxies (default for all classes in Hibernate 3), Hibernate needs to subclass your class at runtime. It can't do this if you have a private no-argument constructor. As per documentation, at least package visibility is required." It just seems logical to put some of this information into the exception itself and save some people some time. The faq is informative, but why can't the exception message just say the same thing. Seems like a big run around to me. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2008