You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Max R. A. (JIRA) <no...@at...> - 2006-07-25 14:11:12
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-710?page=all ] Max Rydahl Andersen updated HBX-710: ------------------------------------ Component: ant eclipse Fix Version: 3.2beta7 Version: 3.2beta6 > "newbie" user error messages > ---------------------------- > > Key: HBX-710 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-710 > Project: Hibernate Tools > Type: Improvement > Components: eclipse, ant > Versions: 3.2beta6 > Reporter: Max Rydahl Andersen > Fix For: 3.2beta7 > > -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Max R. A. (JIRA) <no...@at...> - 2006-07-25 14:00:13
|
"newbie" user error messages ---------------------------- Key: HBX-710 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-710 Project: Hibernate Tools Type: Improvement Reporter: Max Rydahl Andersen -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Max R. A. (JIRA) <no...@at...> - 2006-07-25 09:21:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941?page=comments#action_23758 ] Max Rydahl Andersen commented on HHH-1941: ------------------------------------------ something like: throw InvalidMappingException with type and path. e.g. "resource", "org/some/package/Blah" where today its just a generic MappingException throw MappingNotFoundException (will in some cases be the cause for the above) with similar type and path when it can be identified that it is simply not there. > Be more specific about x not found and invalid mapping exceptions to allow tools to tell about it > ------------------------------------------------------------------------------------------------- > > Key: HHH-1941 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.2.0.cr3 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 3.2.0.ga > > > We are getting more and more questions about the classical "invalid mapping" and/or "resource not found" exceptions when people are using the tools. > I suggest we improve the exceptions so the tooling can give more qualified hints on what is missing/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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Max R. A. (JIRA) <no...@at...> - 2006-07-25 09:18:15
|
Be more specific about x not found and invalid mapping exceptions to allow tools to tell about it ------------------------------------------------------------------------------------------------- Key: HHH-1941 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.cr3 Reporter: Max Rydahl Andersen Fix For: 3.2.0.ga We are getting more and more questions about the classical "invalid mapping" and/or "resource not found" exceptions when people are using the tools. I suggest we improve the exceptions so the tooling can give more qualified hints on what is missing/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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Max R. A. (JIRA) <no...@at...> - 2006-07-25 09:18:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941?page=all ] Max Rydahl Andersen reassigned HHH-1941: ---------------------------------------- Assign To: Max Rydahl Andersen > Be more specific about x not found and invalid mapping exceptions to allow tools to tell about it > ------------------------------------------------------------------------------------------------- > > Key: HHH-1941 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1941 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.2.0.cr3 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 3.2.0.ga > > > We are getting more and more questions about the classical "invalid mapping" and/or "resource not found" exceptions when people are using the tools. > I suggest we improve the exceptions so the tooling can give more qualified hints on what is missing/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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Christian B. (JIRA) <no...@at...> - 2006-07-25 08:55:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1940?page=comments#action_23757 ] Christian Bauer commented on HHH-1940: -------------------------------------- The benchmarks, execution plans, and result numbers for the most important 5 databases would be enough. > many-to-one fetch="join|select" > ------------------------------- > > Key: HHH-1940 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1940 > Project: Hibernate3 > Type: New Feature > Components: core > Reporter: Erik Mathijs > Priority: Minor > > > if you specify fetch="join" the related object will be loaded using a outer join. > It would be more performant if you can specify the type of join (outer join, inner join) for example fetch="inner join". > You can use the fetch="inner join' on foreign key fields that are not null fields in the database table. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Christian B. (JIRA) <no...@at...> - 2006-07-25 08:53:12
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1940?page=comments#action_23756 ] Christian Bauer commented on HHH-1940: -------------------------------------- Please attach benchmarks, SQL execution plans, and result numbers that show that an inner join is a better option for a non-null key two tuple join. > many-to-one fetch="join|select" > ------------------------------- > > Key: HHH-1940 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1940 > Project: Hibernate3 > Type: New Feature > Components: core > Reporter: Erik Mathijs > Priority: Minor > > > if you specify fetch="join" the related object will be loaded using a outer join. > It would be more performant if you can specify the type of join (outer join, inner join) for example fetch="inner join". > You can use the fetch="inner join' on foreign key fields that are not null fields in the database table. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Erik M. (JIRA) <no...@at...> - 2006-07-25 08:44:14
|
many-to-one fetch="join|select" ------------------------------- Key: HHH-1940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1940 Project: Hibernate3 Type: New Feature Components: core Reporter: Erik Mathijs Priority: Minor if you specify fetch="join" the related object will be loaded using a outer join. It would be more performant if you can specify the type of join (outer join, inner join) for example fetch="inner join". You can use the fetch="inner join' on foreign key fields that are not null fields in the database table. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-25 00:31:14
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-395?page=comments#action_23755 ] Emmanuel Bernard commented on ANN-395: -------------------------------------- @Target() > @Embedded can not map interface > ------------------------------- > > Key: ANN-395 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-395 > Project: Hibernate Annotations > Type: Bug > Versions: 3.2.0.cr1 > Reporter: Daniel Tabuenca > > > When configuring with HBM/XML a component you can use the class="com.MyClassImpl" to especify the implementation class for a component property. This would be equivalent to something like. > @Embedded(targetEntity=MyClassImpl.class) > MyClassInterface getMyClass(){ > return myClass; > } > While I know this is not part of the EJB3 spec, being that it is a feature in hibernate when using hbm/xml there should be a simple way to do this with annotations without having to resort to custom user types. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Alex B. (JIRA) <no...@at...> - 2006-07-24 23:44:13
|
@JoinColumn referencedColumnName does not find columns that are not directly in the associated entity ----------------------------------------------------------------------------------------------------- Key: ANN-400 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-400 Project: Hibernate Annotations Type: Bug Components: binder Environment: 3.2.0.CR1 Reporter: Alex Bacon Priority: Minor I attempted to use @JoinColumn(referencedColumnName="id") to map to a property that was not in the associated entity class directly but rather in a MappedSuperclass that the entity extends. It did not find it. Stepping through the code it appears that in org.hibernate.cfg.BinderHelper in the Annotations project - the method findPropertiesByColumns is not finding properties that are not directly in the associated entity - it is not searching MappedSuperclasses as well. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Christian B. (JIRA) <no...@at...> - 2006-07-24 23:42:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-7?page=comments#action_23754 ] Christian Bauer commented on ANN-7: ----------------------------------- That was one of the problems we knew would happen with modularization. For now the best we can do is trying to find the most important issues (all over again) and to add at least references. Later on (in a year or so) we might be able to merge the documentation. > Document usage of @IndexColumn in one-to-many with indexed collection > --------------------------------------------------------------------- > > Key: ANN-7 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-7 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.2.0.cr1 > Environment: Hibernate 3.0.5, Hibernate Annotations 3.0 beta2 preview, HSQL DB > Reporter: Ronald Wildenberg > Assignee: Emmanuel Bernard > Priority: Minor > > > I have a mapping for a List that does not result in the index column of the database table to be filled. > @Entity > public class A { > @OneToMany(mappedBy = "a") > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > public List<B> getBs() { > return bs; > } > public void setBs(List<B> bs) { > this.bs = bs; > } > } > @Entity > public class B { > > @ManyToOne(optional = false) > @JoinColumn(name = "a_id") > public A getA() { > return a; > } > public void setA(A a) { > this.a = a; > } > } > Using this mapping, the 'index' column for table B is never filled if I add B objects to A and save them. > The weird thing is, if I change the mapping for getBs to the following: > @OneToMany > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > an association table is created with columns a_id, b_id, index. The only change I made is removing the mappedBy attribute. This association table is not necessary, since an index column can be added to table B. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Jason B. (JIRA) <no...@at...> - 2006-07-24 23:19:18
|
Extended support for mixing table-per-subclass and table-per-hierarchy ---------------------------------------------------------------------- Key: HHH-1939 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1939 Project: Hibernate3 Type: Improvement Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3, Postgresql 8.1 Reporter: Jason Bennett http://forum.hibernate.org/viewtopic.php?t=962067 At present, Hibernate allows limited mixing of table-per-hierarchy and table-per-subclass. Specifically, once a particular inheritance branch begins using TPS, it cannot switch back to TPH. In our domain (as described in the above forum post), we have several fine-grained objects near the top of our hierarchy, with some bulkier objects lower down. What we would like to do is to run TPS for the higher, smaller classes (where we have referential integrity reasons to break them out), and then switch back to table-per-hierarchy further down, where the majority of our queries are run. I would be happy to assist in implementation, given some direction. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-24 21:41:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-7?page=comments#action_23753 ] Emmanuel Bernard commented on ANN-7: ------------------------------------ yes, but more generally, this means that people do not read HAN reference guide on top of Core ref guide but rather instead of. adapt the annotations reference guide will require a lot of work > Document usage of @IndexColumn in one-to-many with indexed collection > --------------------------------------------------------------------- > > Key: ANN-7 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-7 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.2.0.cr1 > Environment: Hibernate 3.0.5, Hibernate Annotations 3.0 beta2 preview, HSQL DB > Reporter: Ronald Wildenberg > Assignee: Emmanuel Bernard > Priority: Minor > > > I have a mapping for a List that does not result in the index column of the database table to be filled. > @Entity > public class A { > @OneToMany(mappedBy = "a") > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > public List<B> getBs() { > return bs; > } > public void setBs(List<B> bs) { > this.bs = bs; > } > } > @Entity > public class B { > > @ManyToOne(optional = false) > @JoinColumn(name = "a_id") > public A getA() { > return a; > } > public void setA(A a) { > this.a = a; > } > } > Using this mapping, the 'index' column for table B is never filled if I add B objects to A and save them. > The weird thing is, if I change the mapping for getBs to the following: > @OneToMany > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > an association table is created with columns a_id, b_id, index. The only change I made is removing the mappedBy attribute. This association table is not necessary, since an index column can be added to table B. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-24 21:39:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-7?page=comments#action_23752 ] Emmanuel Bernard commented on ANN-7: ------------------------------------ http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#collections-indexedbidirectional > Document usage of @IndexColumn in one-to-many with indexed collection > --------------------------------------------------------------------- > > Key: ANN-7 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-7 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.2.0.cr1 > Environment: Hibernate 3.0.5, Hibernate Annotations 3.0 beta2 preview, HSQL DB > Reporter: Ronald Wildenberg > Assignee: Emmanuel Bernard > Priority: Minor > > > I have a mapping for a List that does not result in the index column of the database table to be filled. > @Entity > public class A { > @OneToMany(mappedBy = "a") > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > public List<B> getBs() { > return bs; > } > public void setBs(List<B> bs) { > this.bs = bs; > } > } > @Entity > public class B { > > @ManyToOne(optional = false) > @JoinColumn(name = "a_id") > public A getA() { > return a; > } > public void setA(A a) { > this.a = a; > } > } > Using this mapping, the 'index' column for table B is never filled if I add B objects to A and save them. > The weird thing is, if I change the mapping for getBs to the following: > @OneToMany > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > an association table is created with columns a_id, b_id, index. The only change I made is removing the mappedBy attribute. This association table is not necessary, since an index column can be added to table B. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Christian B. (JIRA) <no...@at...> - 2006-07-24 21:39:14
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-7?page=all ] Christian Bauer updated ANN-7: ------------------------------ Summary: Document usage of @IndexColumn in one-to-many with indexed collection (was: @IndexColumn does not result in valid index column) type: Improvement (was: Bug) Version: 3.2.0.cr1 (was: 3.1beta3) Priority: Minor (was: Major) > Document usage of @IndexColumn in one-to-many with indexed collection > --------------------------------------------------------------------- > > Key: ANN-7 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-7 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.2.0.cr1 > Environment: Hibernate 3.0.5, Hibernate Annotations 3.0 beta2 preview, HSQL DB > Reporter: Ronald Wildenberg > Assignee: Emmanuel Bernard > Priority: Minor > > > I have a mapping for a List that does not result in the index column of the database table to be filled. > @Entity > public class A { > @OneToMany(mappedBy = "a") > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > public List<B> getBs() { > return bs; > } > public void setBs(List<B> bs) { > this.bs = bs; > } > } > @Entity > public class B { > > @ManyToOne(optional = false) > @JoinColumn(name = "a_id") > public A getA() { > return a; > } > public void setA(A a) { > this.a = a; > } > } > Using this mapping, the 'index' column for table B is never filled if I add B objects to A and save them. > The weird thing is, if I change the mapping for getBs to the following: > @OneToMany > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > an association table is created with columns a_id, b_id, index. The only change I made is removing the mappedBy attribute. This association table is not necessary, since an index column can be added to table B. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Christian B. (JIRA) <no...@at...> - 2006-07-24 21:37:14
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-7?page=all ] Christian Bauer reopened ANN-7: ------------------------------- Assign To: Emmanuel Bernard An example of this needs to be added to the HAN reference documentation that also explains why there is no other way to do it. > @IndexColumn does not result in valid index column > -------------------------------------------------- > > Key: ANN-7 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-7 > Project: Hibernate Annotations > Type: Bug > Components: binder > Versions: 3.1beta3 > Environment: Hibernate 3.0.5, Hibernate Annotations 3.0 beta2 preview, HSQL DB > Reporter: Ronald Wildenberg > Assignee: Emmanuel Bernard > > > I have a mapping for a List that does not result in the index column of the database table to be filled. > @Entity > public class A { > @OneToMany(mappedBy = "a") > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > public List<B> getBs() { > return bs; > } > public void setBs(List<B> bs) { > this.bs = bs; > } > } > @Entity > public class B { > > @ManyToOne(optional = false) > @JoinColumn(name = "a_id") > public A getA() { > return a; > } > public void setA(A a) { > this.a = a; > } > } > Using this mapping, the 'index' column for table B is never filled if I add B objects to A and save them. > The weird thing is, if I change the mapping for getBs to the following: > @OneToMany > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > an association table is created with columns a_id, b_id, index. The only change I made is removing the mappedBy attribute. This association table is not necessary, since an index column can be added to table B. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Max R. A. (JIRA) <no...@at...> - 2006-07-24 21:01:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=comments#action_23750 ] Max Rydahl Andersen commented on HBX-709: ----------------------------------------- doesn't this prevent us from having an update site with all the files ? > 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 > 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Max R. A. (JIRA) <no...@at...> - 2006-07-24 20:55:36
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_23749 ] Max Rydahl Andersen commented on HHH-1293: ------------------------------------------ We can just say that it only occurs on a certain vm implementation and on a certain OS .... > java.lang.NoSuchMethodError: <persistent class>.getHibernateLazyInitializer() > ----------------------------------------------------------------------------- > > Key: HHH-1293 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293 > Project: Hibernate3 > Type: Bug > Versions: 3.1.1 > Reporter: Andreas Schildbach > Assignee: Scott Marlow > Priority: Blocker > Fix For: 3.2.0.ga > Attachments: CGLIBLazyInitializer.patch, CGLIBLazyInitializer.patch, CGLIBLazyInitializer.patch3, CGLIBLazyInitializer.patch4, CGLIBProxyFactory.patch3, hibernate3.jar, manysessions.tgz > > > As documented in > http://forum.hibernate.org/viewtopic.php?t=940119 > some people (including me) are getting this exception with the final release of Hibernate 3.1: > java.lang.NoSuchMethodError: de.schildbach.game.integration.HibernateGamePlayer.getHibernateLazyInitializer()Lorg/hibernate/proxy/LazyInitializer; > at de.schildbach.game.integration.HibernateGamePlayer$$EnhancerByCGLIB$$afecb986.getHibernateLazyInitializer(<generated>) > at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:274) > at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) > at org.hibernate.type.TypeFactory.assemble(TypeFactory.java:398) > at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:96) > at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:82) > at org.hibernate.event.def.DefaultLoadEventListener.assembleCacheEntry(DefaultLoadEventListener.java:520) > at org.hibernate.event.def.DefaultLoadEventListener.loadFromSecondLevelCache(DefaultLoadEventListener.java:474) > at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:328) > at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) > at org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:202) > at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:169) > at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) > at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:869) > at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:838) > at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) > at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) > at org.hibernate.collection.PersistentList.initializeFromCache(PersistentList.java:378) > at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) > at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627) > at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) > at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) > at org.hibernate.collection.AbstractPersistentCollection.readSize(AbstractPersistentCollection.java:109) > at org.hibernate.collection.PersistentList.size(PersistentList.java:91) > The exception varies with the actual persistent class in use. Most people seem to be using JDK 1.5 and Linux. Some reports say that the exception does not happen from the very start of the application, but it takes "several invocations"/"some time" until it appear, but then it appears very often. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-24 20:52:53
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938?page=all ] Emmanuel Bernard updated HHH-1938: ---------------------------------- Summary: Proxy creation may fails when duplicate methods are used by the compiler (was: Proxy creation may fails when duplicate methods are allowed) > Proxy creation may fails when duplicate methods are used by the compiler > ------------------------------------------------------------------------ > > Key: HHH-1938 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Minor > > > http://jira.jboss.com/jira/browse/JASSIST-24 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Guido L. (JIRA) <no...@at...> - 2006-07-24 20:32:18
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-7?page=comments#action_23748 ] Guido Laures commented on ANN-7: -------------------------------- I agree with James and Ronald. I finally manged to get an indexed list persisted by removing the mappedBy attribute. Before this the index column was NULL permanently. But it is not correctly implemented as every indexed one-to-many association seems to result in a cross reference table, which is not necessary and produces unnessecary updates during insert. Please fix this. > @IndexColumn does not result in valid index column > -------------------------------------------------- > > Key: ANN-7 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-7 > Project: Hibernate Annotations > Type: Bug > Components: binder > Versions: 3.1beta3 > Environment: Hibernate 3.0.5, Hibernate Annotations 3.0 beta2 preview, HSQL DB > Reporter: Ronald Wildenberg > > > I have a mapping for a List that does not result in the index column of the database table to be filled. > @Entity > public class A { > @OneToMany(mappedBy = "a") > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > public List<B> getBs() { > return bs; > } > public void setBs(List<B> bs) { > this.bs = bs; > } > } > @Entity > public class B { > > @ManyToOne(optional = false) > @JoinColumn(name = "a_id") > public A getA() { > return a; > } > public void setA(A a) { > this.a = a; > } > } > Using this mapping, the 'index' column for table B is never filled if I add B objects to A and save them. > The weird thing is, if I change the mapping for getBs to the following: > @OneToMany > @Cascade(value = CascadeType.SAVE_UPDATE) > @IndexColumn(name = "index", base = 0) > an association table is created with columns a_id, b_id, index. The only change I made is removing the mappedBy attribute. This association table is not necessary, since an index column can be added to table B. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Scott M. (JIRA) <no...@at...> - 2006-07-24 19:48:48
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=all ] Scott Marlow resolved HHH-1293: ------------------------------- Resolution: Fixed Fix applied to 3.2 branch revision 10146, file org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer. > java.lang.NoSuchMethodError: <persistent class>.getHibernateLazyInitializer() > ----------------------------------------------------------------------------- > > Key: HHH-1293 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293 > Project: Hibernate3 > Type: Bug > Versions: 3.1.1 > Reporter: Andreas Schildbach > Assignee: Scott Marlow > Priority: Blocker > Fix For: 3.2.0.ga > Attachments: CGLIBLazyInitializer.patch, CGLIBLazyInitializer.patch, CGLIBLazyInitializer.patch3, CGLIBLazyInitializer.patch4, CGLIBProxyFactory.patch3, hibernate3.jar, manysessions.tgz > > > As documented in > http://forum.hibernate.org/viewtopic.php?t=940119 > some people (including me) are getting this exception with the final release of Hibernate 3.1: > java.lang.NoSuchMethodError: de.schildbach.game.integration.HibernateGamePlayer.getHibernateLazyInitializer()Lorg/hibernate/proxy/LazyInitializer; > at de.schildbach.game.integration.HibernateGamePlayer$$EnhancerByCGLIB$$afecb986.getHibernateLazyInitializer(<generated>) > at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:274) > at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) > at org.hibernate.type.TypeFactory.assemble(TypeFactory.java:398) > at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:96) > at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:82) > at org.hibernate.event.def.DefaultLoadEventListener.assembleCacheEntry(DefaultLoadEventListener.java:520) > at org.hibernate.event.def.DefaultLoadEventListener.loadFromSecondLevelCache(DefaultLoadEventListener.java:474) > at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:328) > at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) > at org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:202) > at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:169) > at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) > at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:869) > at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:838) > at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) > at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) > at org.hibernate.collection.PersistentList.initializeFromCache(PersistentList.java:378) > at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) > at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627) > at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) > at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) > at org.hibernate.collection.AbstractPersistentCollection.readSize(AbstractPersistentCollection.java:109) > at org.hibernate.collection.PersistentList.size(PersistentList.java:91) > The exception varies with the actual persistent class in use. Most people seem to be using JDK 1.5 and Linux. Some reports say that the exception does not happen from the very start of the application, but it takes "several invocations"/"some time" until it appear, but then it appears very often. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Darryl M. (JIRA) <no...@at...> - 2006-07-24 19:00:49
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=all ] Darryl Miles updated HBX-709: ----------------------------- Attachment: feature.xml Damn, Sorry JIRA wont let me edit the Priority to something more suitable once I've posted the issue. Please find attached a working new feature.xml file for 3.2.0.beta6a. > 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 > 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Darryl M. (JIRA) <no...@at...> - 2006-07-24 18:53:01
|
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 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-24 18:14:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938?page=all ] Emmanuel Bernard reassigned HHH-1938: ------------------------------------- Assign To: Steve Ebersole (was: Emmanuel Bernard) waiting for javassist > Proxy creation may fails when duplicate methods are allowed > ----------------------------------------------------------- > > Key: HHH-1938 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Minor > > > http://jira.jboss.com/jira/browse/JASSIST-24 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-24 18:04:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938?page=all ] Emmanuel Bernard updated HHH-1938: ---------------------------------- Summary: Proxy creation may fails when duplicate methods are allowed (was: Proxy creation may fails when duplciate methods are allowed) > Proxy creation may fails when duplicate methods are allowed > ----------------------------------------------------------- > > Key: HHH-1938 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > > > http://jira.jboss.com/jira/browse/JASSIST-24 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |