May 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-613) NPE when mappedBy property is wrong on a @OneToOne

by Emmanuel Bernard (JIRA)

NPE when mappedBy property is wrong on a @OneToOne -------------------------------------------------- Key: ANN-613 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-613 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: Version assumed, the user did not said it explicitly Reporter: Emmanuel Bernard -- 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

17 years, 5 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-1999) DirtyCollectionSearchVisitor.processCollection fails on dom4j collection

by Nelis Bijl (JIRA)

DirtyCollectionSearchVisitor.processCollection fails on dom4j collection ------------------------------------------------------------------------ Key: HHH-1999 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1999 Project: Hibernate3 Type: Bug Versions: 3.1.3 Environment: SQL server 9.0.1399 Reporter: Nelis Bijl The test in above mentioned function: if ( type.isArrayType()) { is not correct in case of a document element being used as collection holder. I could temporary fix things by using 'type.isCollectionType()' but I am not sure whether that is appropriate. Perhaps '!(type instanceof PersistenCollection)' could be an option. -- 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

17 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-284) Scanning for META-INF/orm.xml does not work in Windows environment due to different in path-separator

by Gary Ip (JIRA)

Scanning for META-INF/orm.xml does not work in Windows environment due to different in path-separator ----------------------------------------------------------------------------------------------------- Key: EJB-284 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-284 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: Windows XP SP2 Tomcat 5.2.23 Spring 2.0.3 Hibernate Core 3.2.2.GA Hibernate Annotations 3.3.0.GA Hibernate EntityManager 3.3.1.GA Reporter: Gary Ip In org.hibernate.ejb.Ejb3Configuration: line: 606, method scanForXmlFiles(...), Iterator it = ArchiveBrowser.getBrowser( jar, new ArchiveBrowser.Filter() { public boolean accept(String filename) { return (searchforHBMFiles && filename.endsWith( ".hbm.xml" ) ) || (searchforORMFiles && filename.endsWith( META_INF_ORM_XML ) ) ; } } filename passed in use "/" in *NIX environment, while "\" is used in Win32 environment. So orm.xml will be ignored in Win32 environment, as it will end with META-INF\orm.xml and won't be matched. -- 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

17 years, 5 months

3
13
0 / 0

[Hibernate-JIRA] Created: (EJB-233) Move from JBoss Archive browser to VFS

by Emmanuel Bernard (JIRA)

Move from JBoss Archive browser to VFS -------------------------------------- Key: EJB-233 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-233 Project: Hibernate Entity Manager Type: Task Components: EntityManager Reporter: Emmanuel Bernard HEM uses the JBoss ArchiveBrowser to scan a particular jar. This needs to be switched to the org.jboss.virtual.* set of interfaces as it is duplicating functionality. -- 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

17 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-430) @ManyToOne results in default outer join eager fetch, should be lazy

by Christian Bauer (JIRA)

@ManyToOne results in default outer join eager fetch, should be lazy -------------------------------------------------------------------- Key: ANN-430 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-430 Project: Hibernate Annotations Type: Bug Components: documentation, binder Reporter: Christian Bauer Documentation says: <sect3> <title>Association fetching</title> <para>You have the ability to either eagerly or lazily fetch associated entities. The <literal>fetch</literal> parameter can be set to <literal>FetchType.LAZY</literal> or <literal>FetchType.EAGER</literal>. <literal>EAGER</literal> will try to use an outer join select to retrieve the associated object, while <literal>LAZY</literal> is the default and will only trigger a select when the associated object is accessed for the first time. EJBQL also has a <literal>fetch</literal> keyword that allows you to override laziness when doing a particular query. This is very useful to improve performance and is decided on a use case to use case basis.</para> </sect3> However, a simple @ManyToOne without any other attributes results in an eager join outer fetch. -- 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

17 years, 6 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-41) Allow different analyzers for each class

by Caleb Land (JIRA)

Allow different analyzers for each class ---------------------------------------- Key: HSEARCH-41 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-41 Project: Hibernate Search Issue Type: New Feature Components: mapping Environment: hibernate-search-3.0.0.beta1 Reporter: Caleb Land Priority: Minor It would be useful to allow the user to specify different Lucene analyzers to use for each @Indexed class. If this is a feature that the hibernate-search developers would be interested in, I wouldn't mind writing tests and implementing it. I've hacked together a version of this that works by simply adding a "analyzer" parameter to the @Indexed annotation, and then reading that in SearchFactory in the loop that iterates over the class mappings, but while it suits my purposes, I don't think it's a good, general purpose solution. Any ideas? -- 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

17 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2279) Cannot fully disable integration with Hibernate Validator

by Jacek Chleborowicz (JIRA)

Cannot fully disable integration with Hibernate Validator --------------------------------------------------------- Key: HHH-2279 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2279 Project: Hibernate3 Type: Improvement Components: metamodel Versions: 3.2.0.cr2 Reporter: Jacek Chleborowicz Priority: Minor I use Hibernate Validator for application-level validation. I disabled pre-insert and pre-update event listeners from Hibernate Validator. I allow persisting data, which doesn't match validation rules defined by Hibernate Validator annotations. Unfortunately Hibernate Validator is used in metamodel construction and i cannot disable it. For example, if i use @NotNull annotation, i've got: PropertyValueException with message "not-null property references a null or transient value: ...", because @NotNull annotation is recognized in metamodel construction. There should be configuration property defining if Hibernate integrates with Hibernate Validator. It should enable/disable: - usage of Hibernate Validator in metamodel construction; - registration of Validator event listeners. -- 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

17 years, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-1995) NPE on evict after update

by Nelis Bijl (JIRA)

NPE on evict after update ------------------------- Key: HHH-1995 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1995 Project: Hibernate3 Type: Bug Versions: 3.1.3 Environment: Hibernate 3.1, SQL Server 9.0.1399 Reporter: Nelis Bijl Attachments: A.hbm.xml I am a newby and investigating the dom4j feature (XML <-> DB). When I try to evict after an update I get a NullPointerException at org.hibernate.event.def.EvictVisitor.evictCollection(EvictVisitor.java:50) This is caused by the fact that the update did not call addCollectionHolder whereas the error location tries to use the result of removeCollectionHolder. Attached you will find the used hbm.xml. The collectionholder is root node A. -- 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

17 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2235) Support for null map-keys in <map> mappings

by Igor Lobanov (JIRA)

Support for null map-keys in <map> mappings ------------------------------------------- Key: HHH-2235 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2235 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Reporter: Igor Lobanov Priority: Minor I'm not sure if I should file it as a bug. Hibernate requires index column for <map> mappings to be not null. This is required by the code in AbstractCollectionPersister#readIndex(...), which raises exception if index column is null. However, when I override collection persister and force readIndex method to return null, everything seems to work fine. Hibernate allows me to work with maps using null value as a key. Though I havn't tested it extensivly yet. What is the reason for disallowing null values as a keys? If there are possible complicated error conditions, then this issue is a feature request for null-values support for <map> mappings. If there are no errors possible, then constraining such behavior is probably wrong. -- 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

17 years, 6 months

4
21
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-18) ShardedSessionImpl.replicate(Object obj, ReplicationMode replicationMode);

by Max Ross (JIRA)

ShardedSessionImpl.replicate(Object obj, ReplicationMode replicationMode); -------------------------------------------------------------------------- Key: HSHARDS-18 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-18 Project: Hibernate Shards Issue Type: Task Components: engine Affects Versions: 3.0.0.Beta1 Reporter: Max Ross Assignee: Max Ross Fix For: 3.0.0.beta2 -- 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

17 years, 6 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2007