September 2006 - hibernate-issues

[Hibernate-JIRA] Commented: (ANN-103) Allow to specify fetching strategy for secondary table

by Amir Pashazadeh (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-103?page=co... ] Amir Pashazadeh commented on ANN-103: ------------------------------------- But I believe the optional="false" is a necessity too. Cause with optional="false" and @SecondaryTables and SingleTable inheritance strategy we could have joined subclasses with discriminator values. > Allow to specify fetching strategy for secondary table > ------------------------------------------------------ > > Key: ANN-103 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-103 > Project: Hibernate Annotations > Type: New Feature > Components: binder > Reporter: Christian Bauer > Priority: Minor > > > Right now a secondary table always defaults to optional="true" and fetch="join". I don't see a real value in optional="false" anyway, but fetch="select" might be useful. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2095) Very large method cannot be instrumented if the instrumented method is larger than 64 Kb

by Peter Schütt (JIRA)

Very large method cannot be instrumented if the instrumented method is larger than 64 Kb ---------------------------------------------------------------------------------------- Key: HHH-2095 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2095 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.2 Environment: Windows 2000, Linux, different databases Reporter: Peter Schütt Very large method cannot be instrumented if the instrumented method is larger than 64 Kb. I know that only stupid programmer created such large methods. But this problem can be happened if hibernate is used together with generated classes. -- 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, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2096) Doing Runtime-Enhancing during the build time

by Peter Schütt (JIRA)

Doing Runtime-Enhancing during the build time --------------------------------------------- Key: HHH-2096 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2096 Project: Hibernate3 Type: Improvement Components: core Versions: 3.1.2 Environment: Windows 2000, Linux, different databases Reporter: Peter Schütt If a project decided to use build time instrumenting because of not using PoJos then it seems to be stupid to instrument them again during runtime. If you have many persistent classes (a few hundred) than it costs many time to enhance them during runtime and it is more performant to instrument them completely during build time -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1739) HILO id can cause deadlock: Part deux

by Martin Slava (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1739?page=c... ] Martin Slava commented on HHH-1739: ----------------------------------- Hi, I have the same problem too. There is a problem with database connection closing in org.hibernate.engine.transaction.Isolater. In nested class method JdbcDelegate.delegateWork() is issue in finally block. Code session.getBatcher().closeConnection( connection ); must be out of the if statement block. This issue is fixed in version 3.2 RC4. MS > HILO id can cause deadlock: Part deux > ------------------------------------- > > Key: HHH-1739 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1739 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3 > Environment: Hibernate 3.1.3 running JDK 1.4.1_07 Solaris 5.8 > Adaptive Server Enterprise/12.5.2/EBF 12054 ESD#2/P/Sun_svr4/OS 5.8/ase1252/1844/64-bit/FBO/Thu Aug 12 10:51:11 2004 > Reporter: Kirk Rasmussen > > Original Estimate: 1 minute > Remaining: 1 minute > > This is mostly a duplicate of HB-1246 but with a twist. I believe that there is a flaw in Hibernate's design for how it generates ids for some dialects. This is a particular problem for deep object graphs and/or at high volume. Or at least it is a problem for those of us stuck on the crappy Sybase platform. > We have an application that creates hundreds of objects that need ids generated within a single transaction. It is quite common for us to potentially exhaust the connection pool with a deep object graph. We are persisting a Trade object which has a complex and deep object graph (upwards of 100s of persistent objects). Within each trade there are roughly 15 classes which need generated ids with 30 or more instances of each class in some cases. > IMO The design flaw is when the ids are generated. From quickly browsing the source it seems that they are being generated on the fly as the objects are being processed. This can result in running of out database connections when under load or when a particular trade has a large number of persistent object instances and deadlocking the system. > A better design would be if the ids could be generated for all tables in a single transaction up front rather than issuing a whole bunch of individual transactions for each table and object. > I believe that TOPLink generates all its ids up front to avoid the described resource thrashing. It also has the configuration to generate ids from within the same transaction as the original unit of work or from a secondary unit of work. > See org.hibernate.id.MultipleHiLoPerTableGenerator -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-267) hbm2java does not handle <properties> tag correctly

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-267?page=all ] Max Rydahl Andersen updated HBX-267: ------------------------------------ Fix Version: 3.2beta9 (was: 3.2beta8) > hbm2java does not handle <properties> tag correctly > --------------------------------------------------- > > Key: HBX-267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-267 > Project: Hibernate Tools > Type: Patch > Components: hbm2java > Versions: 3.0alpha > Environment: Hibernate Tools from CVS > Reporter: Jason Boutwell > Fix For: 3.2beta9 > Attachments: PropertiesUsage.java, failingtest.zip, patch.txt, patch.txt > > > If an hbm <class> mapping contains a <properties> tag, hbm2java creates a POJO that contains only the child properties of the <properties> logical element. All other elements in the class mapping are discarded. I've looked at the source code, and, while not intimate with it, I speculate that hbm2java is treating <properties> like <component> and overwriting the actual entity POJO with a component POJO. Is this a bug, or is the <properties> tag explicitly not yet supported? -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-446) one-to-many relation with not-null attribute on key element

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-446?page=all ] Max Rydahl Andersen updated HBX-446: ------------------------------------ Fix Version: 3.2beta9 (was: 3.2beta8) > one-to-many relation with not-null attribute on key element > ----------------------------------------------------------- > > Key: HBX-446 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-446 > Project: Hibernate Tools > Type: Bug > Components: hbm2java > Environment: 3.x > Reporter: Sreeram Katta > Priority: Critical > Fix For: 3.2beta9 > > > one-to-many relation with not-null attribute on key element is throwing below error when I run the hbm2java tool. I have a base class with a joined-subclass and the joined subclass has one-to-many relationship with another class. The one-to-many uses a list. When I specify not-null attribute on the key element in the relationship I get the below error. If I remove it I don't get this error. If I let the key stay not-null, during run time persistence fails. So I had to revert the mapping file at runtime for the persistence to go fine. It is only the tool that is misbehaving. > ----------------> Error > org.hibernate.tool.hbm2x.ExporterException: Error while processing t > emplate pojo/javaclass.vm > at org.apache.tools.ant.Task.perform(Task.java:373) > at org.apache.tools.ant.Target.execute(Target.java:341) > at org.apache.tools.ant.Target.performTasks(Target.java:369) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) > at org.apache.tools.ant.Project.executeTarget(Project.java:1185) > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) > at org.apache.tools.ant.Project.executeTargets(Project.java:1068) > at org.apache.tools.ant.Main.runBuild(Main.java:668) > at org.apache.tools.ant.Main.startAnt(Main.java:187) > at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) > at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) > Caused by: org.hibernate.tool.hbm2x.ExporterException: Error while processing template pojo/javaclass.vm > at org.hibernate.tool.hbm2x.TemplateHelper.processTemplate(TemplateHelper.java:89) > at org.hibernate.tool.hbm2x.POJOExporter.runVelocity(POJOExporter.java:78) > at org.hibernate.tool.hbm2x.POJOExporter.exportPersistentClass(POJOExporter.java:61) > at org.hibernate.tool.hbm2x.POJOExporter.start(POJOExporter.java:111) > at org.hibernate.tool.ant.GeneratorTask.execute(GeneratorTask.java:33) > at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:115) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > at org.apache.tools.ant.Task.perform(Task.java:364) > ----------------- > mapping files > -----------> Base class > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" > > <hibernate-mapping package="test.resources.core"> > <class > name="Resource" > table="Resource" polymorphism="explicit" > > > <id > name="Id" > type="integer" > column="resourceId" > > > <meta attribute="use-in-equals">true</meta> > <generator class="hilo"> > <param name="table">ResourceIdTracker</param> > <param name="column">resourceId</param> > </generator> > </id> > <property > name="ResourceName" > column="resourceName" > type="string" > not-null="true" > length="80" > /> > <property > name="ResourceDescription" > column="resourceDescription" > type="string" > not-null="true" > length="255" > /> > <property > name="ResourceTypeId" > column="resourceTypeId" > type="integer" > not-null="true" > length="10" > /> > <property > name="CreatedBy" > column="createdBy" > type="integer" > not-null="true" > length="10" > /> > <property > name="CreatedTime" > column="createdTime" > type="timestamp" > not-null="true" > length="23" > /> > <property > name="LastUpdatedBy" > column="lastUpdatedBy" > type="integer" > not-null="true" > length="10" > /> > <property > name="LastUpdatedTime" > column="lastUpdatedTime" > type="timestamp" > not-null="true" > length="23" > /> > <property > name="Deleted" > column="deleted" > type="string" > not-null="true" > length="1" > /> > <set name="ResourcePermissions" table="ResourcePermission" inverse="true"> > <key column="resourceId" not-null="true"/> > <one-to-many class="ResourcePermission"/> > </set> > </class> > </hibernate-mapping> > --------------------> JOINED SUBCLASS > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" > > <hibernate-mapping package="test.resources.chartbook"> > <joined-subclass > name="ChartDefinition" > table="ChartDefinition" > extends="test.resources.core.Resource" > > > <key column="chartDefinitionId"/> > <property > name="FromDate" > column="fromDate" > type="integer" > not-null="false" > length="10" > /> > <property > name="ToDate" > column="toDate" > type="integer" > not-null="false" > length="10" > /> > <property > name="Period" > column="period" > type="string" > not-null="false" > length="32" > /> > <property > name="ViewType" > column="viewType" > type="string" > not-null="false" > length="32" > /> >  > <one-to-one name="chartAxisDefinition" cascade="all-delete-orphan" class="ChartAxisDefinition"/> >  >  >  >  > <list name="ChartSeries" cascade="all-delete-orphan" inverse="false" lazy="false"> > <key column="chartDefinitionId" not-null="true"/> > <list-index column="position" /> > <one-to-many class="ChartSeries"/> > </list> > </joined-subclass> > </hibernate-mapping> > --------------> ONE TO MANY TARGET > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" > > <hibernate-mapping package="test.resources.chartbook"> > <class > name="ChartSeries" > table="ChartSeries" > > > <id > name="Id" > type="integer" > column="chartSeriesId" > > > <generator class="hilo"> > <param name="table">ResourceIdTracker</param> > <param name="column">resourceId</param> > </generator> > </id> > <property > name="Included" > column="included" > type="string" > not-null="true" > length="1" > /> > <property > name="SelectorTreeNodePath" > column="selectorTreeNodePath" > type="string" > not-null="false" > length="1024" > /> > <property > name="Attribute" > column="attribute" > type="string" > not-null="false" > length="50" > /> > <property > name="ColumnName" > column="columnName" > type="string" > not-null="false" > length="255" > /> > <property > name="Formula" > column="formula" > type="string" > not-null="false" > /> > <property > name="AxisLocation" > column="axisLocation" > type="string" > not-null="true" > length="32" > /> > <property > name="Position" > column="position" > type="integer" > not-null="true" > length="10" > insert="false" > update="false" > /> > </class> > </hibernate-mapping> > -------------- ONE TO ONE TARGET > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" > > <hibernate-mapping package="test.resources.chartbook"> > <class > name="ChartAxisDefinition" > table="ChartAxisDefinition" > > > <id > name="Id" > type="integer" > column="chartAxisDefinitionId" > > > <generator class="foreign"> > <param name="property">ChartDefinition</param> > </generator> > </id> > <property > name="LeftAxisMin" > column="leftAxisMin" > type="java.lang.Double" > not-null="true" > length="15" > /> > <property > name="LeftAxisMax" > column="leftAxisMax" > type="java.lang.Double" > not-null="true" > length="15" > /> > <property > name="RightAxisMin" > column="rightAxisMin" > type="java.lang.Double" > not-null="true" > length="15" > /> > <property > name="RightAxisMax" > column="rightAxisMax" > type="java.lang.Double" > not-null="true" > length="15" > /> > <property > name="LeftAxisLabel" > column="leftAxisLabel" > type="string" > not-null="true" > length="32" > /> > <property > name="RightAxisLabel" > column="rightAxisLabel" > type="string" > not-null="true" > length="32" > /> > <property > name="ChartName" > column="chartName" > type="string" > not-null="true" > length="80" > /> > <one-to-one name="ChartDefinition" class="ChartDefinition" constrained="true"/> > </class> > </hibernate-mapping> -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-288) "Generate 'raw' composite ids" setting for Ant script

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-288?page=all ] Max Rydahl Andersen updated HBX-288: ------------------------------------ Fix Version: 3.2beta9 (was: 3.2beta8) > "Generate 'raw' composite ids" setting for Ant script > ----------------------------------------------------- > > Key: HBX-288 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-288 > Project: Hibernate Tools > Type: Bug > Components: reverse-engineer > Versions: 3.0alpha4 > Environment: Windows XP, Hibernate 3.0, Hibernate Tools 3.0 alpha4, Oracle 10g > Reporter: Jason > Fix For: 3.2beta9 > > > According to te documentation the Eclipse Plugin contains a settings on the reverse enginerring UI called "Generate 'raw' composite ids", though there is no equivilant setting for the ant script. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-500) Externalize string literals

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-500?page=all ] Max Rydahl Andersen updated HBX-500: ------------------------------------ Fix Version: 3.2beta9 (was: 3.2beta8) > Externalize string literals > --------------------------- > > Key: HBX-500 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-500 > Project: Hibernate Tools > Type: Improvement > Components: eclipse > Versions: 3.1beta1 > Reporter: Naoki Takezoe > Priority: Critical > Fix For: 3.2beta9 > > > Is it possible to externalize string literals for internationalization? > If externalized that once, contributors can provide resource bundles of many languages. > Of course, I can make this patch. However I think this patch will cross many parts of UI codes. > So even if I (or someone) make this patch, that will become impossible to apply soon. > By the way, Hibernate Eclipse Plugin is very good! I'm looking forward to future releases. > Regards. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-597) New Hibernate Configuration wizard is missing the Classpath list

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-597?page=all ] Max Rydahl Andersen updated HBX-597: ------------------------------------ Fix Version: 3.2beta9 (was: 3.2beta8) > New Hibernate Configuration wizard is missing the Classpath list > ---------------------------------------------------------------- > > Key: HBX-597 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-597 > Project: Hibernate Tools > Type: Improvement > Reporter: Christian Bauer > Priority: Critical > Fix For: 3.2beta9 > > > The "New Hibernate Configuration" wizard that opens up when I click "Create Console Configuration" in the "New Hibernate XML Configuration file" wizard does not have the "Classpath" list. The created Hibernate Console configuration is therefore unusable. You have to actually Edit it again in the Console perspective and add the POJO classpath. This additional Edit step has to be avoided, either the created console configuration works or the wizard is useless. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-600) make templates resistant towards unset properties

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-600?page=all ] Max Rydahl Andersen updated HBX-600: ------------------------------------ Fix Version: 3.2beta9 (was: 3.2beta8) > make templates resistant towards unset properties > ------------------------------------------------- > > Key: HBX-600 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-600 > Project: Hibernate Tools > Type: Improvement > Components: hbm2java > Versions: 3.1beta4 > Reporter: Max Rydahl Andersen > Fix For: 3.2beta9 > > > e..g jdk5 and ejb3 is expected to be configured by the templates. > we should safeguard them with template code that initializes these values if they are not present -- 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, 3 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 September 2006