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: Emmanuel B. (JIRA) <no...@at...> - 2006-07-24 18:00:20
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1937?page=all ] Emmanuel Bernard resolved HHH-1937: ----------------------------------- Fix Version: 3.2.0.ga Resolution: Fixed Steve, check revision r10143 and r10144 > Proxy creation failure leads to NPEs > ------------------------------------ > > Key: HHH-1937 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1937 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0.ga > > > When proxy factory creation fails, the factory is set to null but the lazy state is still set to true. > This leads to NPEs when Hibernate use the factory later on at runtime -- 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 17:48:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_23743 ] Scott Marlow commented on HHH-1293: ----------------------------------- The patch is a change to how the implementation works that avoids the bug (as suggested above byJuozas Baliuka.) We would need to isolate the failure further to determine if a JVM bug is the root cause. Sun would need a small test case that demonstrates the bug with an explanation of what is occurring in the test case. Then, Sun would be able to debug the JVM code while running the simple test case. I cannot answer your question about whether there is or isn't a JVM bug at this point. > 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: Muthu (JIRA) <no...@at...> - 2006-07-24 17:22:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1479?page=comments#action_23742 ] Muthu commented on HHH-1479: ---------------------------- Related issue can be found here http://forum.hibernate.org/viewtopic.php?t=960818&highlight= > Incompatibility of Hibernate 3.1 and JTOpen JDBC drivers for IBM AS/400 > ----------------------------------------------------------------------- > > Key: HHH-1479 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1479 > Project: Hibernate3 > Type: Patch > Versions: 3.1 > Environment: Hibernate 3.1 > JDBC driver: JTOpen (for IBM AS/400) http://jt400.sourceforge.net > Reporter: Davide Rogora > > > Hello, > I've noticed that from version 3.1 Hibernate, when calling JDBC driver for INSERT statement, uses the following prepareStatement method: > prepareStatement(String sql, String[] columnNames) > instead of the following > prepareStatement(String sql, int autoGeneratedKeys) > used since versione 3.0.x > the problem is that JDBC driver for AS/400 (project JTOpen on sourceforge: http://jt400.sourceforge.net) doesn't support the method prepareStatement(String sql, String[] columnNames) so it's not possible to use Hibernate 3.1 with AS/400 > I've also noticed that other open source drivers that support this method (for example MySQL Jdbcconnector or JTDS for Ms-SQLServer) have implemented it using a workaround; infact they call the "old" prepareStatement(String sql, int autoGeneratedKeys) method ignoring the content of the columnNames array. > Here is the source of the jtds implementation: > ------------------------------------------------------------------------------- > public PreparedStatement prepareStatement(String sql, String[] columnNames) > throws SQLException { > if (columnNames == null) { > throw new SQLException( > Messages.get("error.generic.nullparam", "prepareStatement"),"HY092"); > } else if (columnNames.length != 1) { > throw new SQLException( > Messages.get("error.generic.needcolname", "prepareStatement"),"HY092"); > } > return prepareStatement(sql, JtdsStatement.RETURN_GENERATED_KEYS); > } > ------------------------------------------------------------------------------- > So I'm asking to the Hibernate team if it's possible to use the old method prepareStatement(String sql, int autoGeneratedKeys) in the future releases of Hibernate. > Thanks, > Davide Rogora. -- 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: Muthu (JIRA) <no...@at...> - 2006-07-24 17:20:12
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1479?page=comments#action_23741 ] Muthu commented on HHH-1479: ---------------------------- We had same issue too. We replaced org.hibernate.util.GetGeneratedKeysHelper of 3.1 with one from 3.0 and re-jared it. It works fine now. > Incompatibility of Hibernate 3.1 and JTOpen JDBC drivers for IBM AS/400 > ----------------------------------------------------------------------- > > Key: HHH-1479 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1479 > Project: Hibernate3 > Type: Patch > Versions: 3.1 > Environment: Hibernate 3.1 > JDBC driver: JTOpen (for IBM AS/400) http://jt400.sourceforge.net > Reporter: Davide Rogora > > > Hello, > I've noticed that from version 3.1 Hibernate, when calling JDBC driver for INSERT statement, uses the following prepareStatement method: > prepareStatement(String sql, String[] columnNames) > instead of the following > prepareStatement(String sql, int autoGeneratedKeys) > used since versione 3.0.x > the problem is that JDBC driver for AS/400 (project JTOpen on sourceforge: http://jt400.sourceforge.net) doesn't support the method prepareStatement(String sql, String[] columnNames) so it's not possible to use Hibernate 3.1 with AS/400 > I've also noticed that other open source drivers that support this method (for example MySQL Jdbcconnector or JTDS for Ms-SQLServer) have implemented it using a workaround; infact they call the "old" prepareStatement(String sql, int autoGeneratedKeys) method ignoring the content of the columnNames array. > Here is the source of the jtds implementation: > ------------------------------------------------------------------------------- > public PreparedStatement prepareStatement(String sql, String[] columnNames) > throws SQLException { > if (columnNames == null) { > throw new SQLException( > Messages.get("error.generic.nullparam", "prepareStatement"),"HY092"); > } else if (columnNames.length != 1) { > throw new SQLException( > Messages.get("error.generic.needcolname", "prepareStatement"),"HY092"); > } > return prepareStatement(sql, JtdsStatement.RETURN_GENERATED_KEYS); > } > ------------------------------------------------------------------------------- > So I'm asking to the Hibernate team if it's possible to use the old method prepareStatement(String sql, int autoGeneratedKeys) in the future releases of Hibernate. > Thanks, > Davide Rogora. -- 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 17:18:18
|
Proxy creation may fails when duplciate 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 Assigned to: 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 |
From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-24 17:18:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938?page=comments#action_23740 ] Emmanuel Bernard commented on HHH-1938: --------------------------------------- update Javassist when its release goes live > Proxy creation may fails when duplciate 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 |
From: Christopher G. S. II (JIRA) <no...@at...> - 2006-07-24 17:12:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1848?page=all ] Christopher G. Stach II updated HHH-1848: ----------------------------------------- Attachment: HHH-1848.patch Voila. > A session.lock generates a query with a version column in a joined subclass which does not exist > ------------------------------------------------------------------------------------------------ > > Key: HHH-1848 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1848 > Project: Hibernate3 > Type: Bug > Versions: 3.2.0.cr2 > Environment: Windows XP Pro SP2 (full update) > Java 1.5.0_06 > Postgres 8.1 > postgresql-8.1-404.jdbc3.jar > Annotations 3.2.0 cr1 > hibernatetools-3.1.0.beta5 > Reporter: Eduard Mossinkoff > Priority: Minor > Attachments: HHH-1848.patch, screenshot-1.jpg, screenshot-1.jpg > > > A joined class hierarchy using annotations has a version property named "optlock" like in the annotation reference. > The session factory in the Eclipse Hibernate console shows the joined subclass and it contains the "id" and "version" properties inherited from its superclass. The generated schema only has the version property in the table representing the root entity. The subclass has no "optlock" column. Now when a session.lock() is called with an instance of the subclass as its parameter and lockmode "UPGRADE", a query is generated including the "optlock" column on the subclass table which doesn't exist in the schema. > The root entity, only showing the relevant properties > @Entity > @Inheritance(strategy = InheritanceType.JOINED) > @AccessType("field") > public class ModelObject implements Serializable, AccessControl { > private static final long serialVersionUID = 2354579396538279696L; > transient public static final int STORAGE_COSTS = 10; > @Id > @GeneratedValue(generator = "system-uuid") > @GenericGenerator(name = "system-uuid", strategy = "uuid") > private String id; > @Version > @Column(name="optlock") > private Integer version; > } > A sub class > @Entity > @AccessType("field") > public class Item extends ModelObject implements Cloneable, Serializable { > } > @Entity > @AccessType("field") > public class Domain extends Item { > protected String domainId = null; > } > @Entity > @AccessType("field") > public class UserDomain extends Domain { > private long lastLoginDate; > } > The Hibernate console shows: > org.across.model.UserDomain > +id:java.lang.String > +version:java.lang.Integer > The database table of ModelObject > CREATE TABLE dev.modelobject > ( > id varchar(255) NOT NULL, > optlock int4, > acl_id varchar(255), > CONSTRAINT modelobject_pkey PRIMARY KEY (id), > CONSTRAINT fk78ba6fa841f3e430 FOREIGN KEY (acl_id) > REFERENCES dev.acl (id) MATCH SIMPLE > ON UPDATE NO ACTION ON DELETE NO ACTION > ) > WITHOUT OIDS; > ALTER TABLE dev.modelobject OWNER TO across; > The UserDomain table > CREATE TABLE dev.userdomain > ( > id varchar(255) NOT NULL, > lastlogindate int8 NOT NULL, > CONSTRAINT userdomain_pkey PRIMARY KEY (id), > CONSTRAINT fkbbd6448faf7c2769 FOREIGN KEY (id) > REFERENCES dev."domain" (id) MATCH SIMPLE > ON UPDATE NO ACTION ON DELETE NO ACTION > ) > WITHOUT OIDS; > ALTER TABLE dev.userdomain OWNER TO across; > The query generated when calling session.lock(userDomain, LockMode.UPGRADE); where userDomain is an instance created in a different session that was closed. > Hibernate: select id from dev.UserDomain where id =? and optlock =? for update > 7625 [main] WARN org.hibernate.util.JDBCExceptionReporter - SQL Error: 0, SQLState: 42703 > 7625 [main] ERROR org.hibernate.util.JDBCExceptionReporter - ERROR: column "optlock" does not exist > The "optlock" column is not present in the UserDomain table only in the ModelObject table. > The question is, is the generated query wrong or is the Hibernate Eclipse tool generating a wrong schema. -- 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: Andreas S. (JIRA) <no...@at...> - 2006-07-24 17:04:35
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_23738 ] Andreas Schildbach commented on HHH-1293: ----------------------------------------- So, is it confirmed that this is no JVM bug, and your patch is really a bugfix and not a workaround? > 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 17:00:18
|
Proxy creation failure leads to NPEs ------------------------------------ Key: HHH-1937 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1937 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr3 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor When proxy factory creation fails, the factory is set to null but the lazy state is still set to true. This leads to NPEs when Hibernate use the factory later on at runtime -- 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: Leonid S. (JIRA) <no...@at...> - 2006-07-24 16:58:14
|
IdentityGenerator doesn't support BigInteger as a valid identity type. ---------------------------------------------------------------------- Key: HHH-1936 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1936 Project: Hibernate3 Type: Bug Components: core Versions: 3.0.5 Environment: Hibernate 3.0.5, Sybase 12.05, Window/ Unix Reporter: Leonid Shtivelman Identity generator strategy doesn't support BigInteger as a valid id type. This causes problem with Sybase which requires identity column to be numeric. It would seem an obvious way to get around this problem is to set column mapping to long in hibernate xml and the actual java object. This will solve obvious problem of creating identity, but will cause performance problem on selection. In order for Sybase to use index for parameter query the variable type of the parameter and column index type has to be the same. If ones maps column type to Long, Hibernate will use JDBC method setLong(long) to set value in the prepared statement. This will cause mismatch between parameter type and column index type, and Sybase will not use index to locate index. As you can see this is a big problem for anyone that is using identity columns Sybase and Hibernate -- 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: Bill J. (JIRA) <no...@at...> - 2006-07-24 15:29:13
|
Hibernate produces invalid "create table" SQL for Maps on SQL Server 2000 ------------------------------------------------------------------------- Key: HHH-1935 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1935 Project: Hibernate3 Type: Bug Versions: 3.2.0.cr2 Environment: Hibernate 3.2.0.cr2 Microsoft SQL Server 2000 Reporter: Bill Johnson I have two cases where Hibernate3 produces invalid SQL for MS SQL Server 2000: Case 1: @CollectionOfElements @org.hibernate.annotations.MapKey protected Map<String, String> properties; Case 2: @ManyToMany @MapKeyManyToMany private Map<A, B> b; In Case 2, A and B are entities creating a ternary relationship between the parent class, A and B, and I get the following log output: ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] - <Unsuccessful: create table A_B (A_id numeric(19,0) not null, b_id numeric(19,0) not null, key_id numeric(19,0) null, primary key (A_id, key_id), unique (key_id))> ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] - <Cannot define PRIMARY KEY constraint on nullable column in table 'A_B'.> Hibernate should not attempt to create a nullable primary key column by default on MS SQL Server. -- 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 15:11:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-708?page=all ] Max Rydahl Andersen closed HBX-708: ----------------------------------- Fix Version: 3.2beta7 Resolution: Fixed fixed. > hbm2hbmxml misorders version,property from annotations > ------------------------------------------------------ > > Key: HBX-708 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-708 > Project: Hibernate Tools > Type: Bug > Components: ant > Versions: 3.2beta6 > Environment: Hibernate Tools 3.2.0.beta6a > Reporter: Nate Franzen > Fix For: 3.2beta7 > Attachments: hibernate.bugreport.zip > > > Creating the mapping files from the annotations puts the xml elements in an invalid order: > <class> > <id/> > <property/> > <version/> > <property/> > </class> > see also http://forum.hibernate.org/viewtopic.php?t=962308 > The attached files reproduce the problem. > Step 1: set the hibernatetools.dir property to the correct value > Step 2: set the xerces.path property to the correct value > run "ant -f hibernate.build.xml" -- 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 13:51:23
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_23736 ] Max Rydahl Andersen commented on HHH-1293: ------------------------------------------ That is the goal yes. And please do realize we have had this one on the radar since the day it were reported....it was not trivial to hunt down a for a time non-reproducable bug on a platform we didn't have main development on ;) > 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: Thom P. (JIRA) <no...@at...> - 2006-07-24 13:43:34
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_23735 ] Thom Pischke commented on HHH-1293: ----------------------------------- Glad to see this issue finally getting some serious attention. I assume that the patch being developed will be in the next 3.2 Release candidate, or at least in the final release of 3.2? > 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: Max R. A. (JIRA) <no...@at...> - 2006-07-24 13:40:14
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934?page=comments#action_23734 ] Max Rydahl Andersen commented on HHH-1934: ------------------------------------------ there is also the issue of us logging and then throwing which we should also avoid. Furthermore in 99% of the cases the class and (definitly the) id will be exactly the same and thus this line is only relevant if they are actually different. And I would say that should actually never be able to happen....(they could of course be one subclass or the other, but its still very rare) I'm not keen on adding that since i haven't seen it being an issue that isn't quicker/better solved with a debugger. > logging NonUniqueObjectException and WrongClassException > -------------------------------------------------------- > > Key: HHH-1934 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Holger Haag > Priority: Trivial > Fix For: 3.2.0.ga > Attachments: hb.patch > > > Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions. -- 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: Holger H. (JIRA) <no...@at...> - 2006-07-24 13:33:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934?page=comments#action_23733 ] Holger Haag commented on HHH-1934: ---------------------------------- Thanks. You're right about the toString() since anything can happen in there. What about removing the implicit toString() calls and only showing the the values of old.getClass().getCanonicalName() and entity.getClass().getCanonicalName() ? > logging NonUniqueObjectException and WrongClassException > -------------------------------------------------------- > > Key: HHH-1934 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Holger Haag > Priority: Trivial > Fix For: 3.2.0.ga > Attachments: hb.patch > > > Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions. -- 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 13:23:13
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934?page=all ] Max Rydahl Andersen closed HHH-1934: ------------------------------------ Fix Version: 3.2.0.ga Resolution: Fixed I applied the wrongclass patch, but the other one i decided not to do since it requires calling "tostring" on the object which we would like to avoid (it could trigger more exceptions) > logging NonUniqueObjectException and WrongClassException > -------------------------------------------------------- > > Key: HHH-1934 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Holger Haag > Priority: Trivial > Fix For: 3.2.0.ga > Attachments: hb.patch > > > Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions. -- 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 12:35:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-399?page=comments#action_23731 ] Emmanuel Bernard commented on ANN-399: -------------------------------------- agreed on the warning but transient fields must be testable by Hibernate Validator > Class validator should not chack Transient fields and methods > ------------------------------------------------------------- > > Key: ANN-399 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-399 > Project: Hibernate Annotations > Type: Improvement > Components: validator > Versions: 3.2.0.cr1 > Reporter: Sergey Vladimirov > Priority: Minor > > > Class validator should not check (and print warnings) about Transient methods and fields: > 24.07 18:17:02 WARN ClassValidator Original type of property public ru.arptek.arpsite.content.Field ru.arptek.arpsite.content.WebObject.getField(java.lang.String) throws ru.arptek.arpsite.data.DataAccessException is unbound and has been approximated. > @Transient > public <T extends Field> T getField(String name) throws DataAccessException -- 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: Holger H. (JIRA) <no...@at...> - 2006-07-24 12:15:13
|
logging NonUniqueObjectException and WrongClassException -------------------------------------------------------- Key: HHH-1934 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1934 Project: Hibernate3 Type: Improvement Components: core Reporter: Holger Haag Priority: Trivial Attachments: hb.patch Added some logging information which make it easier to track down NonUniqueObjectException and WrongClassException exceptions. -- 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 11:30:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1933?page=all ] Christian Bauer resolved HHH-1933: ---------------------------------- Resolution: Rejected Go to http://forum.hibernate.org/ > How will I save object only into child table > ----------------------------------------------- > > Key: HHH-1933 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1933 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Environment: Hibernate 3.1, Oracle 8i > Reporter: Sreekanth K I > Priority: Critical > Attachments: My Issue.zip > > Original Estimate: 1 minute > Remaining: 1 minute > > I have a problem while using Hibernate bi-directional relationship. > My hbm file look like this: > ------------------------------------------------------- > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping package="hibernate"> > <class name="Submissions" table="submission"> > > <id name="submissionId" type="string" unsaved-value="null" > > <column name="submission_id" sql-type="raw(16)" not-null="true"/> > </id> > > <property name="submissionNo"> > <column name="submission_no" sql-type="VARCHAR2(5)" not-null="true"/> > </property> > > <property name="createdTs"> > <column name="created_ts" sql-type="Date" not-null="true"/> > </property> > > <property name="lastModifiedTs"> > <column name="last_modified_ts" sql-type="Date" not-null="true"/> > </property> > > ...... ....... ........ ...... ... > > <many-to-one name="application" insert="false" update="false" class="Application" column="application_id" /> > > </class> > > </hibernate-mapping > > Application.hbm file > --------------------------------- > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping package="hibernate"> > <class name="Application" table="application"> > > <id name="appId" type="string" unsaved-value="null" > > <column name="application_id" sql-type="raw(16)" not-null="true"/> > </id> > > <property name="appName"> > <column name="application_name" sql-type="varchar2(100)" not-null="true"/> > </property> > > <property name="appFolderName"> > <column name="application_folder_name" sql-type="varchar2(2000)" not-null="true"/> > </property> > ........ ...... ....... ....... ..... > > <set name="submissions" inverse="true" cascade="all-delete-orphan"> > <key column="application_id"/> > <one-to-many class="Submissions"/> > </set> > </class> > ------------------------------------------------------------------------------------------------------------ > The problem I nedd to insert a record only into submission table using Hibernate. > My sample code looks like this: > SessionFactory sessionFactory=HibernateFactory.buildsessionFactory(); > Session session= sessionFactory.openSession(); > Transaction tx=HibernateFactory.begintransaction(session); > Submissions oSub=new Submissions(); > // How will I set application id in Submission which has many-to-one relationship to application table > oSub.setSubmissionNo("0005"); > oSub.setCreatedTs(new java.util.Date()); > oSub.setLastModifiedTs(new Date()); > session.saveOrUpdate(oSub); > HibernateFactory.commitTransaction(tx); > System.out.println("Done"); > HibernateFactory.close(session); > How will I set application Id to submission table? > Please do favour with me > Thanks and regards, > Sreekanth -- 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: Sreekanth K I (JIRA) <no...@at...> - 2006-07-24 11:24:16
|
How will I save object only into child table ----------------------------------------------- Key: HHH-1933 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1933 Project: Hibernate3 Type: Bug Components: core Versions: 3.1 Environment: Hibernate 3.1, Oracle 8i Reporter: Sreekanth K I Priority: Critical Attachments: My Issue.zip I have a problem while using Hibernate bi-directional relationship. My hbm file look like this: ------------------------------------------------------- <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="hibernate"> <class name="Submissions" table="submission"> <id name="submissionId" type="string" unsaved-value="null" > <column name="submission_id" sql-type="raw(16)" not-null="true"/> </id> <property name="submissionNo"> <column name="submission_no" sql-type="VARCHAR2(5)" not-null="true"/> </property> <property name="createdTs"> <column name="created_ts" sql-type="Date" not-null="true"/> </property> <property name="lastModifiedTs"> <column name="last_modified_ts" sql-type="Date" not-null="true"/> </property> ...... ....... ........ ...... ... <many-to-one name="application" insert="false" update="false" class="Application" column="application_id" /> </class> </hibernate-mapping > Application.hbm file --------------------------------- <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="hibernate"> <class name="Application" table="application"> <id name="appId" type="string" unsaved-value="null" > <column name="application_id" sql-type="raw(16)" not-null="true"/> </id> <property name="appName"> <column name="application_name" sql-type="varchar2(100)" not-null="true"/> </property> <property name="appFolderName"> <column name="application_folder_name" sql-type="varchar2(2000)" not-null="true"/> </property> ........ ...... ....... ....... ..... <set name="submissions" inverse="true" cascade="all-delete-orphan"> <key column="application_id"/> <one-to-many class="Submissions"/> </set> </class> ------------------------------------------------------------------------------------------------------------ The problem I nedd to insert a record only into submission table using Hibernate. My sample code looks like this: SessionFactory sessionFactory=HibernateFactory.buildsessionFactory(); Session session= sessionFactory.openSession(); Transaction tx=HibernateFactory.begintransaction(session); Submissions oSub=new Submissions(); // How will I set application id in Submission which has many-to-one relationship to application table oSub.setSubmissionNo("0005"); oSub.setCreatedTs(new java.util.Date()); oSub.setLastModifiedTs(new Date()); session.saveOrUpdate(oSub); HibernateFactory.commitTransaction(tx); System.out.println("Done"); HibernateFactory.close(session); How will I set application Id to submission table? Please do favour with me Thanks and regards, Sreekanth -- 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 11:05:15
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1924?page=all ] Max Rydahl Andersen closed HHH-1924: ------------------------------------ Fix Version: 3.2.0.ga Resolution: Fixed thanks. fixed. > ForeignKeys: TransientObjectException is thrown without a message because of a wrong bracket in the code > -------------------------------------------------------------------------------------------------------- > > Key: HHH-1924 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1924 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0.cr3 > Reporter: Manfred Geiler > Priority: Minor > Fix For: 3.2.0.ga > > > Line 216 of org.hibernate.engine.ForeignKeys class is this: > throw new TransientObjectException( > "object references an unsaved transient instance - save the transient instance before flushing: " + > entityName == null ? session.guessEntityName( object ) : entityName > ); > but should rather be this: > throw new TransientObjectException( > "object references an unsaved transient instance - save the transient instance before flushing: " + > (entityName == null ? session.guessEntityName( object ) : entityName) > ); -- 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 10:34:23
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=all ] Max Rydahl Andersen reassigned HHH-1293: ---------------------------------------- Assign To: Scott Marlow (was: Max Rydahl Andersen) back to you. > 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: Max R. A. (JIRA) <no...@at...> - 2006-07-24 10:28:37
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_23727 ] Max Rydahl Andersen commented on HHH-1293: ------------------------------------------ I tried my best to be evil to it, but failed ;) The nightly tests also seem to run through the tests with no issues. It looks like a winner. > 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: Max Rydahl Andersen > 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: Sergey V. (JIRA) <no...@at...> - 2006-07-24 10:18:18
|
Class validator should not chack Transient fields and methods ------------------------------------------------------------- Key: ANN-399 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-399 Project: Hibernate Annotations Type: Improvement Components: validator Versions: 3.2.0.cr1 Reporter: Sergey Vladimirov Priority: Minor Class validator should not check (and print warnings) about Transient methods and fields: 24.07 18:17:02 WARN ClassValidator Original type of property public ru.arptek.arpsite.content.Field ru.arptek.arpsite.content.WebObject.getField(java.lang.String) throws ru.arptek.arpsite.data.DataAccessException is unbound and has been approximated. @Transient public <T extends Field> T getField(String name) throws DataAccessException -- 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 |