[Hibernate-JIRA] Commented: (HBX-709) Start distributing an eclipse Hibernate Tools runtime only JAR
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=co... ]
Max Rydahl Andersen commented on HBX-709:
-----------------------------------------
I don't understand your point about the url's being wrong!? they are links to sites related to these plugins.
I deliberatly did not put an update site pointer in there because we have two; one for stable and another for development (and nightly builds won't work with any of thtem)
We have changed all our external plugin to imports; migrating to features is the next step.
Besides being simpler (fewer) entries does it give us or the user anything else ? (besides maybe getting more plugins than we actually use ;)
> Start distributing an eclipse Hibernate Tools runtime only JAR
> --------------------------------------------------------------
>
> Key: HBX-709
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-709
> Project: Hibernate Tools
> Type: Task
> Reporter: Darryl Miles
> Fix For: 3.2beta8
> Attachments: feature.xml
>
>
> http://forum.hibernate.org/viewtopic.php?t=962374
> Start to pickup and use Eclipse/WTP versioning within the features.xml/
> Plan of action as I see it:
> * Copy features/org.eclipse.* and features.org.apache.* files as well as pre-requisite plugins/* when packaging.
> * Move <plugin ...> into <import ...> in features/org.hibernate.eclipse.feature_3.2.0.beta6a/feature.xml (see attached sample of this working for me)
> * Modify build and packaging process to now create two JARs.
> JAR one contains (this is the runtime only JAR):
> features/org.hibernate.eclipse.feature*
> plugins/org.hibernate.eclipse*
> plugins/org.jboss.ide.eclipse.freemarker*
> JAR two contains (this is the equivalent of what is distrubuted now, hibernate tools, with WTP/XSD/GEF/JEM pre-requisites, without Eclipse Platform)
> All the files in JAR one above, plus
> plugins/org.eclipse.gef*
> plugins/org.eclipse.wst.xml_core.feature.*
> plugins/org.eclipse.wst.common_core.feature*
> plugins/org.eclipse.wst.common_ui.feature*
> plugins/org.apache.xerces.feature*
> plugins/org.eclipse.xsd*
> plugins/org.eclipse.jem*
> plugins/org.eclipse.wst.xml_ui.feature*
> plugins/org.eclipse.emf*
> features/org.eclipse.gef*
> features/org.eclipse.wst.xml_core.feature_*
> features/org.eclipse.wst.common_core.feature_*
> features/org.eclipse.wst.common_ui.feature_*
> features/org.apache.xerces.feature_*
> features/org.eclipse.xsd_*
> features/org.eclipse.jem_*
> features/org.eclipse.wst.xml_ui.feature_*
> features/org.eclipse.emf_*
> By removing the <plugin ..> declarations from the hibernate JAR it stops the JAR claiming it is the authorative source for that plugin to the update manager. By including the original features/ files from the original authorative source means that if a user installs pre-requisites (or has pre-requisites already installed) when they use JAR two, and restart Eclipse will automatically pickup and use the lastest installed version of WTP/XSD/EMF/GEF/JEM compatible with hibernate tools.
> This has the effect is automatically upgrading the version of pre-requisites when multiple versions are found. But in the event the users version of pre-requisites is too old or non-existant then the ones in the JAR two will be picked up and used.
> If the re-packaged version of freemarker is also being used inside other JBOSS plugins, then I would suggest a seperate feature/org.jboss.ide.eclipse.freemarker*/feature.xml be provided and all plugins built on top are then to pickup that with an <import ...> declaration. If hibernate tools is the only user of freemarker then leading it inside hibernate tools is fine.
--
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
19 years, 7 months
[Hibernate-JIRA] Commented: (HBX-709) Start distributing an eclipse Hibernate Tools runtime only JAR
by Darryl Miles (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=co... ]
Darryl Miles commented on HBX-709:
----------------------------------
I have just rebuilt the JbossIDE+HibernateTools from as Nightly build from CVS and I have an update for you.
The original features.xml was not the final version which I put through its paces. Here are the remaining changes:
There update and discovery site URLs are completely wrong, replace that section with this:
<url>
<update label="JBoss/Hibernate Update Site" url="http://download.jboss.org/jbosside/updates/development/"/>
<discovery label="JBoss/Hibernate Update Site" url="http://download.jboss.org/jbosside/updates/development/"/>
</url>
The original features.xml I posted pulled in specific plugin versions by using the plugin="", but after trying a range of configurations I found that to be correct, what you really want to be saying is that HibernatTools relies in the following features.
<import feature="org.eclipse.gef" version="3.2.0" match="greaterOrEqual"/>
<import feature="org.eclipse.wst.xml_core.feature" version="1.5.0" match="greaterOrEqual"/>
<import feature="org.eclipse.wst.common_core.feature" version="1.5.0" match="greaterOrEqual"/>
<import feature="org.eclipse.wst.common_ui.feature" version="1.5.0" match="greaterOrEqual"/>
<import feature="org.apache.xerces.feature" version="2.8.0" match="greaterOrEqual" />
<import feature="org.eclipse.xsd" version="2.2.0" match="greaterOrEqual" />
<import feature="org.eclipse.jem" version="1.2.0" match="greaterOrEqual" />
<import feature="org.eclipse.wst.xml_ui.feature" version="1.5.0" match="greaterOrEqual" />
<import feature="org.eclipse.emf" version="2.2.0" match="greaterOrEqual" />
> Start distributing an eclipse Hibernate Tools runtime only JAR
> --------------------------------------------------------------
>
> Key: HBX-709
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-709
> Project: Hibernate Tools
> Type: Task
> Reporter: Darryl Miles
> Fix For: 3.2beta8
> Attachments: feature.xml
>
>
> http://forum.hibernate.org/viewtopic.php?t=962374
> Start to pickup and use Eclipse/WTP versioning within the features.xml/
> Plan of action as I see it:
> * Copy features/org.eclipse.* and features.org.apache.* files as well as pre-requisite plugins/* when packaging.
> * Move <plugin ...> into <import ...> in features/org.hibernate.eclipse.feature_3.2.0.beta6a/feature.xml (see attached sample of this working for me)
> * Modify build and packaging process to now create two JARs.
> JAR one contains (this is the runtime only JAR):
> features/org.hibernate.eclipse.feature*
> plugins/org.hibernate.eclipse*
> plugins/org.jboss.ide.eclipse.freemarker*
> JAR two contains (this is the equivalent of what is distrubuted now, hibernate tools, with WTP/XSD/GEF/JEM pre-requisites, without Eclipse Platform)
> All the files in JAR one above, plus
> plugins/org.eclipse.gef*
> plugins/org.eclipse.wst.xml_core.feature.*
> plugins/org.eclipse.wst.common_core.feature*
> plugins/org.eclipse.wst.common_ui.feature*
> plugins/org.apache.xerces.feature*
> plugins/org.eclipse.xsd*
> plugins/org.eclipse.jem*
> plugins/org.eclipse.wst.xml_ui.feature*
> plugins/org.eclipse.emf*
> features/org.eclipse.gef*
> features/org.eclipse.wst.xml_core.feature_*
> features/org.eclipse.wst.common_core.feature_*
> features/org.eclipse.wst.common_ui.feature_*
> features/org.apache.xerces.feature_*
> features/org.eclipse.xsd_*
> features/org.eclipse.jem_*
> features/org.eclipse.wst.xml_ui.feature_*
> features/org.eclipse.emf_*
> By removing the <plugin ..> declarations from the hibernate JAR it stops the JAR claiming it is the authorative source for that plugin to the update manager. By including the original features/ files from the original authorative source means that if a user installs pre-requisites (or has pre-requisites already installed) when they use JAR two, and restart Eclipse will automatically pickup and use the lastest installed version of WTP/XSD/EMF/GEF/JEM compatible with hibernate tools.
> This has the effect is automatically upgrading the version of pre-requisites when multiple versions are found. But in the event the users version of pre-requisites is too old or non-existant then the ones in the JAR two will be picked up and used.
> If the re-packaged version of freemarker is also being used inside other JBOSS plugins, then I would suggest a seperate feature/org.jboss.ide.eclipse.freemarker*/feature.xml be provided and all plugins built on top are then to pickup that with an <import ...> declaration. If hibernate tools is the only user of freemarker then leading it inside hibernate tools is fine.
--
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
19 years, 7 months
[Hibernate-JIRA] Commented: (HBX-419) hbm2java w/ ejb3=true does not produce ids w/ unique = true
by Dennis C. Byrne (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-419?page=co... ]
Dennis C. Byrne commented on HBX-419:
-------------------------------------
Max, why was this changed to patch, I only submitted a test to prove the existence.
BTW, we started using that "Patch" feature in JIRA and the idea didn't really take off.
> hbm2java w/ ejb3=true does not produce ids w/ unique = true
> -----------------------------------------------------------
>
> Key: HBX-419
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-419
> Project: Hibernate Tools
> Type: Patch
> Components: hbm2java
> Versions: 3.2LATER
> Environment: Eclipse 3.1 , hibernate.jar and hibernate-tools.jar from the sep. 28 nightly build of JBOSS IDE
> Reporter: Dennis C. Byrne
> Priority: Minor
> Attachments: AnnotationsTestCase.tar
>
>
> http://forum.hibernate.org/viewtopic.php?p=2264112#2264112
> unique is set to false for identifer properties using hbm2java .
> @Id( generate=GeneratorType.NONE)
> @Column(name="person_id", unique=false, nullable=false, insertable=true, updatable=true, ...
> public Long getPersonId() {
> return this.personId;
> }
--
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
19 years, 7 months
[Hibernate-JIRA] Closed: (HBX-670) When there are composite keys JBoss Seam Skeleton App [beta] exporter throws an error "Expression field.value.typeName is undefined on line 35, column 6 in seam/find.jsp.ftl"
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-670?page=all ]
Max Rydahl Andersen closed HBX-670:
-----------------------------------
Resolution: Incomplete
i tried to apply this to the recent version but still errors...any chance you have updated the fix for the latest version ?
> When there are composite keys JBoss Seam Skeleton App [beta] exporter throws an error "Expression field.value.typeName is undefined on line 35, column 6 in seam/find.jsp.ftl"
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBX-670
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-670
> Project: Hibernate Tools
> Type: Patch
> Components: hbm2seam
> Versions: 3.1.beta5
> Environment: JBossIDE1.6GA, Eclipse 3.1.2, Hibernate 3.1, Oracle 10i, Linux amd64
> Reporter: Deyan Bontchev
> Priority: Blocker
> Attachments: editorbean.java.ftl, find.jsp.ftl
>
>
> If there are composite keys in the database schema, the JBoss Seam Skeleton App [beta] exporter throws an error when parse composite identifier property:
> !ENTRY org.hibernate.eclipse 1 10000 2006-06-01 09:17:37.364
> !MESSAGE DEBUG Worker-0 org.hibernate.tool.hbm2x.TemplateHelper - putInContext pojo=org.hibernate.tool.hbm2x.pojo.EntityPOJOClass(persistence.data.UserFlow)
> !ENTRY org.hibernate.eclipse 1 10000 2006-06-01 09:17:37.377
> !MESSAGE DEBUG Worker-0 org.hibernate.tool.hbm2x.TemplateHelper - putInContext clazz=org.hibernate.mapping.RootClass(persistence.data.UserFlow)
> !ENTRY org.hibernate.eclipse 4 40000 2006-06-01 09:17:37.381
> !MESSAGE ERROR Worker-0 freemarker.runtime -
> !STACK 0
> Expression field.value.typeName is undefined on line 35, column 6 in seam/find.jsp.ftl.
> The problematic instruction:
> ----------
> ==> if-else [on line 35, column 1 in seam/find.jsp.ftl]
> ----------
> Java backtrace for programmers:
> ----------
> freemarker.core.InvalidReferenceException: Expression field.value.typeName is undefined on line 35, column 6 in seam/find.jsp.ftl.
> at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
> at freemarker.core.ComparisonExpression.isTrue(ComparisonExpression.java:121)
> at freemarker.core.IfBlock.accept(IfBlock.java:80)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.MixedContent.accept(MixedContent.java:92)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.ConditionalBlock.accept(ConditionalBlock.java:79)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.IteratorBlock$Context.runLoop(IteratorBlock.java:160)
> at freemarker.core.Environment.visit(Environment.java:351)
> at freemarker.core.IteratorBlock.accept(IteratorBlock.java:95)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.MixedContent.accept(MixedContent.java:92)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.Environment.process(Environment.java:176)
> at freemarker.template.Template.process(Template.java:231)
> at org.hibernate.tool.hbm2x.TemplateHelper.processTemplate(TemplateHelper.java:243)
> at org.hibernate.tool.hbm2x.TemplateProducer.produceToString(TemplateProducer.java:67)
> at org.hibernate.tool.hbm2x.TemplateProducer.produce(TemplateProducer.java:28)
> at org.hibernate.tool.hbm2x.TemplateProducer.produce(TemplateProducer.java:97)
> at org.hibernate.tool.hbm2x.GenericExporter.exportPOJO(GenericExporter.java:112)
> at org.hibernate.tool.hbm2x.GenericExporter.exportPersistentClass(GenericExporter.java:101)
> at org.hibernate.tool.hbm2x.GenericExporter.exportClasses(GenericExporter.java:84)
> at org.hibernate.tool.hbm2x.GenericExporter.doStart(GenericExporter.java:69)
> at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:93)
> at org.hibernate.tool.hbm2x.GenericExporter.start(GenericExporter.java:59)
> at org.hibernate.tool.hbm2x.seam.SeamExporter.doStart(SeamExporter.java:65)
> at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:93)
> at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate$1.execute(CodeGenerationLaunchDelegate.java:250)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:35)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:68)
> at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.runExporters(CodeGenerationLaunchDelegate.java:221)
> at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:108)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:590)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:515)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:733)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:931)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> When you fixed this one you will get the similar error when generates Java sources and hits composite identifier property:
> !ENTRY org.hibernate.eclipse 1 10000 2006-06-01 09:10:05.689
> !MESSAGE DEBUG Worker-0 org.hibernate.tool.hbm2x.TemplateHelper - putInContext pojo=org.hibernate.tool.hbm2x.pojo.ComponentPOJOClass(persistence.data.FlowActionId)
> !ENTRY org.hibernate.eclipse 1 10000 2006-06-01 09:10:05.690
> !MESSAGE DEBUG Worker-0 org.hibernate.tool.hbm2x.TemplateHelper - putInContext clazz=org.hibernate.mapping.Component([org.hibernate.mapping.Property(flowCode), org.hibernate.mapping.Property(actionId)])
> !ENTRY org.hibernate.eclipse 4 40000 2006-06-01 09:10:05.693
> !MESSAGE ERROR Worker-0 freemarker.runtime -
> !STACK 0
> Expression pojo.identifierProperty is undefined on line 47, column 6 in seam/editorbean.java.ftl.
> The problematic instruction:
> ----------
> ==> if pojo.identifierProperty.value.identifierGeneratorStrategy == "assigned" [on line 47, column 1 in seam/editorbean.java.ftl]
> ----------
> Java backtrace for programmers:
> ----------
> freemarker.core.InvalidReferenceException: Expression pojo.identifierProperty is undefined on line 47, column 6 in seam/editorbean.java.ftl.
> at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
> at freemarker.core.TemplateObject.invalidTypeException(TemplateObject.java:134)
> at freemarker.core.Dot._getAsTemplateModel(Dot.java:78)
> at freemarker.core.Expression.getAsTemplateModel(Expression.java:89)
> at freemarker.core.Dot._getAsTemplateModel(Dot.java:74)
> at freemarker.core.Expression.getAsTemplateModel(Expression.java:89)
> at freemarker.core.ComparisonExpression.isTrue(ComparisonExpression.java:111)
> at freemarker.core.ConditionalBlock.accept(ConditionalBlock.java:77)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.MixedContent.accept(MixedContent.java:92)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.Environment.visit(Environment.java:233)
> at freemarker.core.BlockAssignment.accept(BlockAssignment.java:83)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.MixedContent.accept(MixedContent.java:92)
> at freemarker.core.Environment.visit(Environment.java:196)
> at freemarker.core.Environment.process(Environment.java:176)
> at freemarker.template.Template.process(Template.java:231)
> at org.hibernate.tool.hbm2x.TemplateHelper.processTemplate(TemplateHelper.java:243)
> at org.hibernate.tool.hbm2x.TemplateProducer.produceToString(TemplateProducer.java:67)
> at org.hibernate.tool.hbm2x.TemplateProducer.produce(TemplateProducer.java:28)
> at org.hibernate.tool.hbm2x.TemplateProducer.produce(TemplateProducer.java:97)
> at org.hibernate.tool.hbm2x.GenericExporter.exportPOJO(GenericExporter.java:112)
> at org.hibernate.tool.hbm2x.GenericExporter.exportComponent(GenericExporter.java:97)
> at org.hibernate.tool.hbm2x.GenericExporter.exportClasses(GenericExporter.java:91)
> at org.hibernate.tool.hbm2x.GenericExporter.doStart(GenericExporter.java:69)
> at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:93)
> at org.hibernate.tool.hbm2x.GenericExporter.start(GenericExporter.java:59)
> at org.hibernate.tool.hbm2x.seam.SeamExporter.doStart(SeamExporter.java:83)
> at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:93)
> at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate$1.execute(CodeGenerationLaunchDelegate.java:250)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:35)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:68)
> at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.runExporters(CodeGenerationLaunchDelegate.java:221)
> at org.hibernate.eclipse.launch.CodeGenerationLaunchDelegate.launch(CodeGenerationLaunchDelegate.java:108)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:590)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:515)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:733)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:931)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
--
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
19 years, 7 months
[Hibernate-JIRA] Commented: (HHH-1217) Problems loading lists of scalar values via EntityMode.DOM4J
by Alexander Kiel (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1217?page=c... ]
Alexander Kiel commented on HHH-1217:
-------------------------------------
I had this issue to. It's right what Craig says. You have to specify a node name.
> Problems loading lists of scalar values via EntityMode.DOM4J
> ------------------------------------------------------------
>
> Key: HHH-1217
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1217
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.0.5
> Environment: HIbernate 3.0.5, MySql 4.10 (Innodb), Windows XP
> Reporter: Patrick Casey
> Fix For: 3.2.2
>
>
> Mappings which contain lists of scalar values (as opposed to lists of mapped objects) throw NPEs when you try to load them via a DOM4J session.
> **The Mapping:
> <class name="metadata.MetaFormDescriptor" table="metaform">
> <cache usage="read-write" />
> <id name="id" type="string" length="32">
> <column name="id" length="32" not-null="true"/>
> <generator class="uuid.hex"/>
> </id>
> <property name="objectClass" column="objectclass" type="string"/>
> <many-to-one name="user" class="core.User" embed-xml="false">
> <column name="user_id" length="32"></column>
> </many-to-one>
> <list name="listA" table="mfa" fetch="join" cascade="all-delete-orphan" embed-xml="false">
> <key column="form_id" />
> <index column="sequence" />
> <element type="string" column="encoded"/>
> </list>
> <list name="listB" table="mfb" fetch="join" cascade="all-delete-orphan" embed-xml="false">
> <key column="form_id" />
> <index column="sequence" />
> <element type="string" column="encoded"/>
> </list>
> <list name="listC" table="mfc" fetch="join" cascade="all-delete-orphan" embed-xml="false">
> <key column="form_id" />
> <index column="sequence" />
> <element type="string" column="encoded"/>
> </list>
> </class>
> **The Code that Loads it:
> Session sxml = snormal.getSession(EntityMode.DOM4J);
> sxml.setFlushMode(FlushMode.NEVER);
> List l = sxml.createQuery("from " + MetaFormDescriptor.class.getCanonicalName()).list();
> ** The Dump you get:
> Exception in thread "main" java.lang.NullPointerException
> at org.dom4j.tree.AbstractElement.addElement(AbstractElement.java:1169)
> at org.hibernate.collection.PersistentIndexedElementHolder.readFrom(PersistentIndexedElementHolder.java:135)
> at org.hibernate.loader.Loader.readCollectionElement(Loader.java:674)
> at org.hibernate.loader.Loader.readCollectionElements(Loader.java:370)
> at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:314)
> at org.hibernate.loader.Loader.doQuery(Loader.java:412)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:218)
> at org.hibernate.loader.Loader.loadCollection(Loader.java:1434)
> at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:99)
> at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:488)
> at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
> at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1430)
> at org.hibernate.type.CollectionType.getCollection(CollectionType.java:484)
> at org.hibernate.type.CollectionType.resolveKey(CollectionType.java:332)
> at org.hibernate.type.CollectionType.resolve(CollectionType.java:326)
> at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:105)
> at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:530)
> at org.hibernate.loader.Loader.doQuery(Loader.java:436)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:218)
> at org.hibernate.loader.Loader.doList(Loader.java:1593)
> at org.hibernate.loader.Loader.list(Loader.java:1577)
> at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:395)
> at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:271)
> at org.hibernate.impl.SessionImpl.list(SessionImpl.java:844)
> at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74)
> at bootstrap.PrimeMover.unLoadOneFile(PrimeMover.java:41)
> at bootstrap.PrimeMover.unLoadSeed(PrimeMover.java:59)
> at zzTest.Tester.main(Tester.java:736)
--
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
19 years, 7 months
[Hibernate-JIRA] Commented: (HHH-794) EntityMode.DOM4J - Multiple many-to-one's to same object can cause incorrect names in XML
by Alexander Kiel (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-794?page=co... ]
Alexander Kiel commented on HHH-794:
------------------------------------
I think this issue is normal. If you have a class A which hase more than one many-to-one rel. to class B, than every XML node will be named equal. The name of the XML node comes from the "node" attribute of the mapping of class B. If you want an other XML node name you can specify it on the many-to-one mapping.
> EntityMode.DOM4J - Multiple many-to-one's to same object can cause incorrect names in XML
> -----------------------------------------------------------------------------------------
>
> Key: HHH-794
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-794
> Project: Hibernate3
> Type: Bug
> Versions: 3.1 beta 1, 3.0.5
> Environment: Windows XP, SQL Server
> Reporter: Preston Sheldon
> Attachments: XMLTestCase.zip
>
>
> An Class that contains 2 many-to-one relationships to the same table, returns an incorrect element name for 1 of the mappings when data is retrieved using EntityMode.DOM4J.
> For example
> Object A has an initialStatus and currentStatus attribute which both map to a Status reference table. In some cases, both elements will be named <currentStatus> even though the data is correct.
> <TestObject>
> <id>1</id>
> <data>Test Data</data>
> <currentStatus> <-- This element should be named <initialStatus>
> <id>1</id>
> <value>Open</value>
> </currentStatus>
> <currentStatus>
> <id>1</id>
> <value>Open</value>
> </currentStatus>
> </TestObject>
--
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
19 years, 7 months
[Hibernate-JIRA] Closed: (HBX-36) Allow Hibernate Console to start with precreated sessionfactory and cfg
by Max Rydahl Andersen (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-36?page=all ]
Max Rydahl Andersen closed HBX-36:
----------------------------------
Resolution: Incomplete
can't work in the current setup...
> Allow Hibernate Console to start with precreated sessionfactory and cfg
> -----------------------------------------------------------------------
>
> Key: HBX-36
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-36
> Project: Hibernate Tools
> Type: New Feature
> Components: consoleconfiguration
> Versions: 2.1
> Environment: Hibern8ide with the hibernate-extensions-2.1.2
> Reporter: Justin Spears
> Priority: Trivial
> Fix For: 3.2LATER
> Attachments: Hibern8IDE.java.patch
>
>
> I am not positive where to add this but have found it really useful.
> Hope ya'll don't mind posting it here, as I am having trouble finding a mailing list regarding this, so apologies in advance.
> The idea is to use the springframework to launch Hibern8ide... This allows one to use their normal spring configuration, and not have to use 2 sets of conf files (1 for spring 1 for hibern8ide) the diff is included, a few trivial changes...
> adding a setSessionFactory and changing the session startup from
> the config to look for the session.
> (you can then do something like this to )
> private static ApplicationContext ctx;
> /** the args are applicationContext*.xml files **/
> public static void main(String[] args) {
> ctx = new ClassPathXmlApplicationContext(args);
> LocalSessionFactoryBean lsfbr = LocalSessionFactoryBean) ctx.getBean("&sessionFactory");
> SessionFactoryImpl sfbr = (SessionFactoryImpl) ctx.getBean("sessionFactory");
>
> Configuration cfg = lsfbr.getConfiguration();
>
> try {
> Hibern8IDE.startWith( cfg, sfbr );
> } catch (HibernateException e) {
> e.printStackTrace();
> }
>
> }
> 227c227
> < sf = configuration.buildSessionFactory();
> ---
> > if (sf == null) sf = configuration.buildSessionFactory();
> 233c233,234
> < }
> ---
> >
> > }
> 336c337
> < DefaultGraphCell target = (DefaultGraphCell) class2Node.get(et.getPersistentClass());
> ---
> > DefaultGraphCell target = (DefaultGraphCell) class2Node.get(et.getAssociatedClass());
> 388a390,396
> >
> > h8ide.start();
> > }
> > public static void startWith(Configuration c, SessionFactory sf) throws HibernateException {
> > Hibern8IDE h8ide = new Hibern8IDE();
> > h8ide.setSessionFactory(sf);
> > h8ide.setConfiguration(c);
> 391d398
> <
> 422c429,430
> < mainWindow.show();
> ---
> > // mainWindow.show();
> > mainWindow.setVisible(true);
> 1040a1049,1060
> > /**
> > * @return Returns the sf.
> > */
> > public SessionFactory getSessionFactory() {
> > return sf;
> > }
> > /**
> > * @param sf The sf to set.
> > */
> > public void setSessionFactory(SessionFactory sf) {
> > this.sf = sf;
> > }
--
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
19 years, 7 months