January 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2863) testsuite fix-ups for maven and/or directory changes

by Steve Ebersole (JIRA)

testsuite fix-ups for maven and/or directory changes ---------------------------------------------------- Key: HHH-2863 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2863 Project: Hibernate3 Issue Type: Bug Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2702) Officially move to JDK 1.4

by Steve Ebersole (JIRA)

Officially move to JDK 1.4 -------------------------- Key: HHH-2702 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2702 Project: Hibernate3 Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 This includes a number of considerations, such as (1) assuming JDBC3 as a baseline, (2) using the improved collections, etc. This will act as the grouping task for all JDK 1.4 migration tasks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2704) Migrate to Maven2 for build

by Steve Ebersole (JIRA)

Migrate to Maven2 for build --------------------------- Key: HHH-2704 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2704 Project: Hibernate3 Issue Type: Task Components: build Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 This is the *official* move to Maven2 issue (since I'm the only one willing to actually do it ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2555) Create new RegionFactory for JBossCache

by Steve Ebersole (JIRA)

Create new RegionFactory for JBossCache --------------------------------------- Key: HHH-2555 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2555 Project: Hibernate3 Issue Type: New Feature Components: caching (L2) Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 Based on discussions ongoing between the Hibernate and JBossCache teams, create a new RegionFactory which takes fulfills the discussed requirements. These requirements are spread throughout: (1) JBC wiki : http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernateAlignment (2) email thread : http://www.mail-archive.com/hibernate-dev%40lists.jboss.org/msg01055.html (plus a few others referenced within the above resources). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-324) Deployed Maven POM incorrectly excludes transitive dependency

by Joe Germuska (JIRA)

Deployed Maven POM incorrectly excludes transitive dependency ------------------------------------------------------------- Key: EJB-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-324 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Maven 2 Reporter: Joe Germuska Priority: Trivial The deployed Maven POM for Hibernate Entity Manager 3.3.1.ga incorrectly excludes the dependency upon the oswego-concurrent libraries (see below). This leads to a NoClassDefFound error: nested exception is java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap Caused by: java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap at org.jboss.util.file.ArchiveBrowser.<clinit>(ArchiveBrowser.java:52) I haven't yet determined how the Maven POMs are being managed by the Hibernate team, but they don't seem to be in Subversion; therefore, I've marked this trivial, although it is a little more than that for someone who is trying to use the Maven repository. In any case, it should be easy to fix. More generally, it might be more correct to employ Maven's ranged version dependency syntax, instead of explicitly excluding other dependencies. excerpt from http://repo1.maven.org/maven2/org/hibernate/hibernate-entitymanager/3.3.1... <dependency> <groupId>jboss</groupId> <artifactId>jboss-common-core</artifactId> <version>2.0.4.GA</version> <exclusions> ... <exclusion> <groupId>oswego-concurrent</groupId> <artifactId>concurrent</artifactId> </exclusion> ... </exclusions> </dependency> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (ANN-607) The source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution.

by Steve Gilbert (JIRA)

The source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution. ------------------------------------------------------------------------------------------- Key: ANN-607 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-607 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.3. Reporter: Steve Gilbert As noted in the summary, the source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2617) Warning on tables with inheritance when table defaults are set in entity-mappings

by Stephen Todd (JIRA)

Warning on tables with inheritance when table defaults are set in entity-mappings --------------------------------------------------------------------------------- Key: HHH-2617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2617 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.2 Environment: Using Annotations Reporter: Stephen Todd Priority: Trivial Attachments: inheritance-orm.xml, TestSingleTableInheritanceWarnings.java The following warning message is logged when entity-mapping defaults are set and tables with inheritance are present: Illegal use of @Table in a subclass of a SINGLE_TABLE hierarchy: class.name.Here I attached a test case that recreates the problem. Basically, the error occurs when a resource contains persistence-unit-defaults. It appears that hibernate creates an @Table attribute for every registered entity when I think it should only do it for non-single table inheritance entities. Below is an example of the orm.xml <entity-mappings> <persistence-unit-metadata> <persistence-unit-defaults> <catalog>public</catalog> </persistence-unit-defaults> </persistence-unit-metadata> <entity class="hibernatebugs.TestAnnotationWarnings$ParentEntity"> <inheritance strategy="SINGLE_TABLE"/> </entity> </entity-mappings> Test requires EasyMock and Log4J. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
6
0 / 0

[Hibernate-JIRA] Created: (ANN-610) Copy/paste errors in reference docs

by Christian Bauer (JIRA)

Copy/paste errors in reference docs ----------------------------------- Key: ANN-610 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-610 Project: Hibernate Annotations Issue Type: Bug Components: documentation Reporter: Christian Bauer Priority: Minor The section on bidirectional indexed collections has copy/paste errors. Also, show a List example and drop the map-key example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2457) UnsupportedOperationException with WebSphereExtendedJTATransactionLookup

by Erik Post (JIRA)

UnsupportedOperationException with WebSphereExtendedJTATransactionLookup ------------------------------------------------------------------------ Key: HHH-2457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457 Project: Hibernate3 Type: Bug Versions: 3.2.2 Reporter: Erik Post Using the WebSphereExtendedJTATransactionLookup as transaction manager lookup class results in an UnsupportedOperationException being thrown by WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(). This method is called by JTATransactionFactory.isTransactionInProgress(). Would a solution be to have the TransactionManagerAdapter#getStatus method delegate to the TransactionAdapter#getStatus method? Also see http://forum.hibernate.org/viewtopic.php?t=966463 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

11
13
0 / 0

[Hibernate-JIRA] Created: (HHH-2073) many-to-one join fetch with optional parent causing stray query to fire

by Adam Hardy (JIRA)

many-to-one join fetch with optional parent causing stray query to fire ----------------------------------------------------------------------- Key: HHH-2073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2073 Project: Hibernate3 Type: Bug Reporter: Adam Hardy Priority: Minor Attachments: bugtest.zip I have a call centre application which uses a mature database and is therefore pushing Hibernate to accomplish the mappings I need. The issue here is extra queries that Hibernate is firing where I set up the mapping to do a join in one hit. I am fetching child objects which may or may not have a parent. The child's foreign key points to a non-primary key on the parent. This is not reflected by a foreign key constraint in the database (hence it allows child to have no parent). If the child object has the foreign key 0 instead of null, which is the protocol in this database, then the parent which doesn't exist is not (& cannot) be instantiated, no problem, but then after processing the resultset, Hibernate fires off another query to fetch the parent that it could not find data for in the first query. This is obviously unnecessary in this context and degrades the performance on large searches on this child. I have classified it as minor since I suspect there may be work-arounds but I have not researched that yet. I didn't know whether I could put the mapping XML in the query, so I have attached a simplistic testcase example that demonstrates the problem. The following forum messages are relevant and the latter contains the mappings, which is easier than extracting them out of the testcase zip: http://forum.hibernate.org/viewtopic.php?t=960522 http://forum.hibernate.org/viewtopic.php?t=964211 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1030) Mixed eol chars in generated pojos

by Simon Toens (JIRA)

Mixed eol chars in generated pojos ---------------------------------- Key: HBX-1030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1030 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.0.GA Environment: java Reporter: Simon Toens Priority: Minor Attachments: eol.patch org.hibernate.tool.hbm2x.pojo.ImportContextImpl hardcodes "\r\n" as eol characters for import statements. This is kind of lame, and a problem when using svn with svn:eol-style=native: $ svn add revengtest/ ... A revengtest/src//test/Actor.hbm.xml svn: File 'revengtest/src/test/Actor.java' has inconsistent new lines svn: Inconsistent line ending style Since the rest of the generated pojo uses "\n", why not just use that? Attached is the trivial patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2664) full join not working

by Fabio Tudone (JIRA)

full join not working --------------------- Key: HHH-2664 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2664 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4, 3.1.2 Environment: Any DB, tested on Windows Reporter: Fabio Tudone Attachments: test.jar I get this error when trying to full join: - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: undefined join type 23 at org.hibernate.hql.ast.util.JoinProcessor.toHibernateJoinType(JoinProcessor.java:68) at org.hibernate.hql.ast.HqlSqlWalker.setImpliedJoinType(HqlSqlWalker.java:433) at org.hibernate.hql.antlr.HqlSqlBaseWalker.joinElement(HqlSqlBaseWalker.java:3157) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3067) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2945) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) at com.finantix.test.Main.main(Main.java:63) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2996) Allow expression in a @JoinColumn for a composite foreign key

by Darren Bell (JIRA)

Allow expression in a @JoinColumn for a composite foreign key ------------------------------------------------------------- Key: HHH-2996 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2996 Project: Hibernate3 Issue Type: New Feature Affects Versions: 3.2.5 Environment: hibernate 3.2.5, db2/400 v5r4 Reporter: Darren Bell I am mapping our Mapics COM history with hibernate and have been pretty successful so far, but have hit a stumbling block. There is a table in Mapics that stores history comments for many different other tables, hence each table has a different foreign key. The table is outlined below for those that don't know Mapics ;) COL_NO NAME COL_TYPE LENGTH DP NULL DFT DEFAULT DESCRIPTION 1 GAAENB NUMERIC 2 0 N Y 0 Company number 2 GAGGNB NUMERIC 6 0 N Y 0 Invoice number 3 GAHYNB DECIMAL 7 0 N Y 0 Invoice sequence 4 GAKBNB DECIMAL 5 0 N Y 0 Comment line sequence number 5 GAAKCD CHAR 3 N Y ' ' Language code 6 GAAAD9 CHAR 1 N Y ' ' Internal print only? 7 GAHDTX CHAR 25 N Y ' ' Comment line text 8 GAHXCD CHAR 5 N Y ' ' Comment user reference 9 GADCCD CHAR 1 N Y ' ' Internal header type 10 GACVNB CHAR 7 N Y ' ' Quote/order number 11 GAK4NB DECIMAL 7 0 N Y 0 Shipment header number 12 GAAFAD DECIMAL 3 0 N Y 0 Shipment consolidate seq 13 GALCNB DECIMAL 7 0 N Y 0 Ship release sequence 14 GAAASZ DECIMAL 5 0 N Y 0 Kit release sequence 15 GAAAD2 DECIMAL 7 0 N Y 0 Special charge sequence # 16 GAAD1N CHAR 1 N Y ' ' Text line print control To get the comments from the shipment release we use the following: @OneToMany() @JoinColumns ({ @JoinColumn(name=HistoricalComment.Columns.COMPANY_NUMBER, referencedColumnName=ShipRelease.Columns.COMPANY_NUMBER), @JoinColumn(name=HistoricalComment.Columns.INTERNAL_HEADER_TYPE, referencedColumnName=ShipRelease.Columns.INTERNAL_HEADER_TYPE), @JoinColumn(name=HistoricalComment.Columns.ORDER_NUMBER, referencedColumnName=ShipRelease.Columns.ORDER_NUMBER), @JoinColumn(name=HistoricalComment.Columns.SHIPMENT_HEADER_NUMBER, referencedColumnName=ShipRelease.Columns.SHIPMENT_HEADER_NUMBER), @JoinColumn(name=HistoricalComment.Columns.SHIP_RELEASE_SEQUENCE, referencedColumnName=ShipRelease.Columns.SHIP_RELEASE_SEQUENCE), @JoinColumn(name=HistoricalComment.Columns.KIT_RELEASE_SEQUENCE, referencedColumnName=ShipRelease.Columns.KIT_RELEASE_SEQUENCE) }) @Sort(type=SortType.NATURAL) private SortedSet<HistoricalComment> historicalComments; Which works well, but to the the comments for the ship header the following is needed @OneToMany() @JoinColumns ({ @JoinColumn(name=HistoricalComment.Columns.COMPANY_NUMBER, referencedColumnName=ShipHeader.Columns.COMPANY_NUMBER), @JoinColumn(name=HistoricalComment.Columns.INTERNAL_HEADER_TYPE, referencedColumnName=ShipHeader.Columns.INTERNAL_HEADER_TYPE), @JoinColumn(name=HistoricalComment.Columns.ORDER_NUMBER, referencedColumnName=ShipHeader.Columns.ORDER_NUMBER), @JoinColumn(name=HistoricalComment.Columns.SHIPMENT_HEADER_NUMBER, referencedColumnName=ShipHeader.Columns.SHIPMENT_HEADER_NUMBER) }) @Sort(type=SortType.NATURAL) private SortedSet<HistoricalComment> historicalComments; As you can see there are two keys missing on the second one to many. This has the undesired effect of retriving all the comments for the entire shipment, whether they are related to a relase, the header itself, or charge codes. Now, what i'm suggesting is to allow an expression for one of the join colums. The following would solve the problem. @OneToMany() @JoinColumns ({ @JoinColumn(name=HistoricalComment.Columns.COMPANY_NUMBER, referencedColumnName=ShipRelease.Columns.COMPANY_NUMBER), @JoinColumn(name=HistoricalComment.Columns.INTERNAL_HEADER_TYPE, referencedColumnName=ShipRelease.Columns.INTERNAL_HEADER_TYPE), @JoinColumn(name=HistoricalComment.Columns.ORDER_NUMBER, referencedColumnName=ShipRelease.Columns.ORDER_NUMBER), @JoinColumn(name=HistoricalComment.Columns.SHIPMENT_HEADER_NUMBER, referencedColumnName=ShipRelease.Columns.SHIPMENT_HEADER_NUMBER), @JoinColumn(name=HistoricalComment.Columns.SHIP_RELEASE_SEQUENCE, expression=":shipReleaseSequence > 0"), @JoinColumn(name=HistoricalComment.Columns.KIT_RELEASE_SEQUENCE, expression=":kitReleaseSequence = 0") }) This would put the expressions into the join clause. What do you think? Have i explained this well enough? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (ANN-689) @JoinColumn not quoted for Oracle dialect

by Earnie Dyke (JIRA)

@JoinColumn not quoted for Oracle dialect ----------------------------------------- Key: ANN-689 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-689 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.2.1 Environment: Oracle 10g XE Reporter: Earnie Dyke Within an @Entity I have the following: @ManyToOne(cascase = {}, fetch = FecthType.Lazy) @JoinColumn(name = "`PresentationId`") // Notice the backticks public Presentation getPresentation() { return this.presentation; } the generated SQL for a load is: select ... from PRESENTATION presentati0_ left outer join CSESSION csessions1_ on presentati0_."Id"=csessions1_.PresentationId where ... Notice that PresentationId in csessions1_.PresentationId is NOT quoted. This causes an exception from Oracle: java.sql.SQLException: ORA-00904: "CSESSIONS1_"."PRESENTATIONID": invalid identifier. I added the backticks to all @Column annotations and they work. Also PresentationId is not quoted in the SELECT list either. Earnie! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (ANN-653) Exception when unidirection OneToMany relation defined in Embeded class

by Jifeng Liu (JIRA)

Exception when unidirection OneToMany relation defined in Embeded class ----------------------------------------------------------------------- Key: ANN-653 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-653 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate Core 3.2.5.ga Hibernate Annotations 3.3.0 GA Hibernate EntityManager 3.3.1 GA Reporter: Jifeng Liu Attachments: src.zip I got the following exception when I run the test case in attach file. It seems Hibernate throws Exception when unidirection OneToMany relation defined in Embeded class. Exception in thread "main" org.hibernate.AnnotationException: Illegal attempt to define a @JoinColumn with a mappedBy as sociation: htmlText.images at org.hibernate.cfg.Ejb3JoinColumn.buildJoinColumn(Ejb3JoinColumn.java:152) at org.hibernate.cfg.Ejb3JoinColumn.buildJoinColumns(Ejb3JoinColumn.java:127) at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1178) at org.hibernate.cfg.AnnotationBinder.fillComponent(AnnotationBinder.java:1731) at org.hibernate.cfg.AnnotationBinder.bindComponent(AnnotationBinder.java:1665) at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1544) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:733) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:498) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:277) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1269) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:150) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:888) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:706) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:137) at test.Test.run(Test.java:24) at test.Test.main(Test.java:20) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-330) Calling configure(String) on Ejb3Configuration before addAnnotatedClass(..) breaks callbacks

by Tuure Laurinolli (JIRA)

Calling configure(String) on Ejb3Configuration before addAnnotatedClass(..) breaks callbacks -------------------------------------------------------------------------------------------- Key: EJB-330 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-330 Project: Hibernate Entity Manager Issue Type: Bug Components: Documentation, EntityManager Affects Versions: 3.3.1.GA Environment: Hibernate Core 3.2.5, Hibernate Annotations 3.3.0, Hibernate EntityManager 3.3.1 Reporter: Tuure Laurinolli Attachments: cbtest.tar.gz If configure(String) has been called on Ejb3Configuration before adding more @Entity-annotated classes with addAnnotatedClass, the @PostLoad callbacks of the classes added with addAnnotatedClass do not work. If the class is added with addAnnotatedClass before configure(String) is called, the callbacks work as expected. The documentation at http://www.hibernate.org/hib_docs/entitymanager/reference/en/html/configu... shows a listing where configure(String) is called before addAnnotatedClass, which in my more minimal test case results in the callbacks on the added class not being called. The attached test case extracts a directory cbtest with the following files in it: test.xml, test.sh, test/Something.java and test/Test.java. test.sh compiled and runs the test, provided that necessary jars have been copied to cbtest. The necessary jars are from Hibernate Core 3.2.5, Hibernate Annotations 3.3.0 and Hibernate EntityManager 3.3.1, except for hsqldb.jar, which is needed because the configuration in test.xml expects Hsqldb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-295) mapping-file orm.xml not included

by Georges-Etienne Legendre (JIRA)

mapping-file orm.xml not included --------------------------------- Key: EJB-295 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-295 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Environment: Hibernate Core 3.2.4.GA Hibernate EntityManager 3.3.1.GA Reporter: Georges-Etienne Legendre We have the following situation: A jar library for our entity classes has been created. In it, there are these two files in the META-INF directory: persistence.xml and orm.xml. We define some common queries in the orm.xml file. This library is then used in another project. Because we would like to define other more specialized named queries in this project, we assumed that another orm.xml file (in the META-INF directoty) could be used. Without any workaround, it doesn't work. The entity manager only find/use the orm.xml contained in the library. To make it works, we have to add these 2 lines in the persistence.xml : <mapping-file>/META-INF/orm.xml</mapping-file> <mapping-file>/META-INF/orm.xml</mapping-file> The entity manager then includes both orm.xml files. In JSR 220, chapter 6.2.1.6, it's said: "... A object/relational mapping XML file named orm.xml may be specified in the META-INF directory in the root of the persistence unit or in the META-INF directory of any jar file referenced by the persistence. xml. Alternatively, or in addition, other mapping files may be referenced by the mapping-file elements of the persistence-unit element, and may be present anywhere on the class path." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
13
0 / 0

[Hibernate-JIRA] Created: (ANN-650) Explicitly disallow @Version on @Embedded and throw meaningful Exception

by Chris Bredesen (JIRA)

Explicitly disallow @Version on @Embedded and throw meaningful Exception ------------------------------------------------------------------------ Key: ANN-650 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-650 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate Annotations 3.3.0.GA Hibernate 3.2.2 Hibernate EntityManager 3.3.1.GA Reporter: Chris Bredesen Priority: Minor The above situation should be explicitly checked for and a meaningful exception thrown. Currently, this configuration blows up with the following trace: java.lang.ArrayIndexOutOfBoundsException: -66 at org.hibernate.persister.entity.AbstractEntityPersister.checkVersion(AbstractEntityPersister.java:1855) at org.hibernate.persister.entity.AbstractEntityPersister.generateUpdateString(AbstractEntityPersister.java:1811) at org.hibernate.persister.entity.AbstractEntityPersister.generateUpdateString(AbstractEntityPersister.java:1777) at org.hibernate.persister.entity.AbstractEntityPersister.postConstruct(AbstractEntityPersister.java:2930) at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:409) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:730) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-673) Guaranty column order in genereted schema

by Ivo Danihelka (JIRA)

Guaranty column order in genereted schema ----------------------------------------- Key: ANN-673 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-673 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1, 3.3.1 Environment: Hibernate 3.2.1 and SVN, PostgreSQL 8.1 Reporter: Ivo Danihelka Priority: Minor Attachments: fk-order.path Problem: - AnnotationConfiguration does not define stable ordering for foreign key columns. They then could appear in generated SQL schema in any order. For example, sometimes table foreign key column person_id is before another foreign key column dog_id and sometimes it is behind it. Tool hbm2ddl could be used to see the generated schema. The order of foreign key columns in one table changes when unrelated change is made inside mapping of a different table. Proposed Solution: - Don't base the ordering of foreign keys on hashCode. Base it on tableName+propertyName. A patch against hibernate 3.2.1 is attached (it also backportes #ANN-551 into 3.2.1). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (ANN-591) SchemaExport throws ConcurrentModificationException for entity containing list of lists

by Ivan O'Connor (JIRA)

SchemaExport throws ConcurrentModificationException for entity containing list of lists --------------------------------------------------------------------------------------- Key: ANN-591 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-591 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1 Environment: Hibernate 3.2.1.GA, Oracle 10 Reporter: Ivan O'Connor Attachments: hbm2ddl.zip I have a class, let's call it A, that contains a List of class B. Each instance of B has a List of class C. I'm trying to generate the DDL for this, so I've annotated the code and run it through SchemaExport, which throws a ConcurrentModificationException. My environment: Java 1.5, Oracle 10, Hibernate 3.2.1ga. The problem seems to be caused by having an entity (A) containing an embedded collection (of B), each element of which contains a collection (of C). SchemaExport generates correct DDL when the annotations are modified to make B and/or C an entity, but not when they are both components. I realise this is considered something of an exotic case, but I'd like to know why the DDL doesn't generate. See bugReport.txt in attached zip for further details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-690) Subclass Configuration methods in AnnotationConfiguration for method chaining.

by Emmanuel Bernard (JIRA)

Subclass Configuration methods in AnnotationConfiguration for method chaining. ------------------------------------------------------------------------------ Key: ANN-690 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-690 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.0.ga Reporter: Emmanuel Bernard Fix For: 3.3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (ANN-590) Table name problem

by Eddie Man (JIRA)

Table name problem ------------------ Key: ANN-590 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-590 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1 Reporter: Eddie Man Priority: Critical Attachments: src.zip Problem: When I run the test.Main in the attachment, an mapping exception thrown while passing the annotation: Exception in thread "main" org.hibernate.MappingException: Unable to find column with logical name: customerID in ShoppingBasket at org.hibernate.cfg.Ejb3JoinColumn.checkReferencedColumnsType(Ejb3JoinColumn.java:383) at org.hibernate.cfg.BinderHelper.createSyntheticPropertyReference(BinderHelper.java:88) at org.hibernate.cfg.FkSecondPass.doSecondPass(FkSecondPass.java:63) at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:428) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:286) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at test.Main.main(Main.java:19) But when I change the table name of ShoppingBaskets to "Basket", then the problem solved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

4
11
0 / 0

[Hibernate-JIRA] Created: (ANN-683) AnnotationConfiguration hashCode collisions produce random binding failures

by Tim Smith (JIRA)

AnnotationConfiguration hashCode collisions produce random binding failures --------------------------------------------------------------------------- Key: ANN-683 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-683 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.4, J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20070426, AIX 5.3 Reporter: Tim Smith Priority: Blocker Attachments: hashCode_bug_fix.patch The method AnnotationConfiguration.processFkSecondPassInOrder creates a Comparator that results in FkSecondPass objects being inadvertently removed from the secondPasses list due to an incorrect hashCode comparison. Lines 398 - 401 contain this comparison of hashCodes: else if ( f1.hashCode() == f2.hashCode() ) { compare = 0; } FkSecondPass uses Object.hashCode which has the JavaDoc comment: * As much as is reasonably practical, the hashCode method defined by * class <tt>Object</tt> does return distinct integers for distinct * objects. (This is typically implemented by converting the internal * address of the object into an integer, but this implementation * technique is not required by the * Java<font size="-2"><sup>TM</sup></font> programming language.) In my application I have seen random failures during startup of the application due to the fact that hashCodes for two FkSecondPass instances are the same, the result is that the FkSecondPass.secondPass method is never called and the FK is never bound, resulting in a error like: org.hibernate.MappingException: Foreign key (FK76A5E7CBCC5EDAA3:CLIENT [])) must have same number of columns as the referenced primary key (CLIENTAPPRC98BF18C [OBJECTID]) at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:90) at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:73) at org.hibernate.cfg.Configuration.secondPassCompileForeignKeys(Configuration.java:1263) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1170) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:316) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1269) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:150) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:888) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:416) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) As you can see the FK column on the owning table is empty (as TableBinder.bindFk is not called). This is a blocker for my application as I can not guarantee when the application will boot. It is entirely dependent on the memory state and implementation of the JVM as to whether or not a hashCode collision occurs. The patch is simple, a one-liner, to replace the hashCode comparison with an object equality comparison: else if ( f1 == f2 ) { compare = 0; } I have attached a patch for AnnotationConfiguration to fix this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2728) Calling session.clear() while retrieving objects via an iterator will cause a "LazyInitializationException - No Session" by the CGLIBLazyInitializer

by Metin Göktay (JIRA)

Calling session.clear() while retrieving objects via an iterator will cause a "LazyInitializationException - No Session" by the CGLIBLazyInitializer ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2728 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2728 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Any Reporter: Metin Göktay Priority: Minor Given the following code Iterator stagingIterator = query.iterate("from "+entityName+" where importSourceFile.id = ?", deliveryId); // large result set while (stagingIterator.hasNext()) { Importable staging = stagingIterator.next(); Approvable approvable = this.approve(staging); tmp.add(approvable); i++; if (i % 200 == 0) { LOG.debug("Flushing+Clearing after "+i+" entries."); session.flush(); session.clear(); } } After clearing the session for the first time (resp. after the first 200 entries) the CGLIBInitializer object of next returned HibernateProxy object does not have a session any longer resulting in a "LazyInitializationException - No Session" exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

6
13
0 / 0

[Hibernate-JIRA] Created: (HBX-938) Graphviz support in hbm2doc does not support Any mappings

by Matt Read (JIRA)

Graphviz support in hbm2doc does not support Any mappings --------------------------------------------------------- Key: HBX-938 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-938 Project: Hibernate Tools Issue Type: Bug Components: doc Affects Versions: 3.2beta9 Reporter: Matt Read Ran hbm2doc from with Maven using the following config: <plugin> <artifactId>maven-antrun-plugin</artifactId> <executions> <execution> <phase>generate-sources</phase> <configuration> <tasks> <taskdef name="hibernatetool" classname="org.hibernate.tool.ant.HibernateToolTask" classpathref="maven.test.classpath" /> <hibernatetool destdir="target/hbm2doc"> <configuration configurationfile="src/test/resources/framepersistence/hibernate.cfg.xml" /> <hbm2doc> <property key="dot.executable" value="c:/work/apps/Graphviz/Graphviz/bin/dot.exe"/> </hbm2doc> </hibernatetool> </tasks> </configuration> <goals> <goal>run</goal> </goals> </execution> </executions> </plugin> Which produced the following error - my mappings contain <any> tags. 12:05:55 ERROR freemarker.runtime - Method public java.lang.String org.hibernate.tool.hbm2x.Cfg2HbmTool.getHibernateTypeName(org.hibernate.mapping.Property) threw an exception when invoked on org. hibernate.tool.hbm2x.Cfg2HbmTool@7348e The problematic instruction: ---------- ==> if c2h.getHibernateTypeName(property)?exists [on line 62, column 6 in dot/entitygraph.dot.ftl] in user-directive propertyEdges [on line 32, column 3 in dot/entitygraph.dot.ftl] ---------- Java backtrace for programmers: ---------- freemarker.template.TemplateModelException: Method public java.lang.String org.hibernate.tool.hbm2x.Cfg2HbmTool.getHibernateTypeName(org.hibernate.mapping.Prope rty) threw an exception when invoked on org.hibernate.tool.hbm2x.Cfg2HbmTool@7348e at freemarker.ext.beans.SimpleMethodModel.exec(SimpleMethodModel.java:136) at freemarker.core.MethodCall._getAsTemplateModel(MethodCall.java:93) at freemarker.core.Expression.getAsTemplateModel(Expression.java:89) at freemarker.core.BuiltIn$existsBI._getAsTemplateModel(BuiltIn.java:635) at freemarker.core.BuiltIn$existsBI.isTrue(BuiltIn.java:646) at freemarker.core.ConditionalBlock.accept(ConditionalBlock.java:77) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.IteratorBlock$Context.runLoop(IteratorBlock.java:160) at freemarker.core.Environment.visit(Environment.java:351) at freemarker.core.IteratorBlock.accept(IteratorBlock.java:95) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.Macro$Context.runMacro(Macro.java:164) at freemarker.core.Environment.visit(Environment.java:537) at freemarker.core.UnifiedCall.accept(UnifiedCall.java:128) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.IteratorBlock$Context.runLoop(IteratorBlock.java:160) at freemarker.core.Environment.visit(Environment.java:351) at freemarker.core.IteratorBlock.accept(IteratorBlock.java:95) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.Environment.process(Environment.java:176) at freemarker.template.Template.process(Template.java:231) at org.hibernate.tool.hbm2x.TemplateHelper.processTemplate(TemplateHelper.java:247) at org.hibernate.tool.hbm2x.TemplateProducer.produceToString(TemplateProducer.java:67) at org.hibernate.tool.hbm2x.TemplateProducer.produce(TemplateProducer.java:28) at org.hibernate.tool.hbm2x.TemplateProducer.produce(TemplateProducer.java:97) at org.hibernate.tool.hbm2x.GenericExporter$1.process(GenericExporter.java:30) at org.hibernate.tool.hbm2x.GenericExporter.doStart(GenericExporter.java:126) at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:95) at org.hibernate.tool.hbm2x.DocExporter.generateDot(DocExporter.java:182) at org.hibernate.tool.hbm2x.DocExporter.doStart(DocExporter.java:151) at org.hibernate.tool.hbm2x.AbstractExporter.start(AbstractExporter.java:95) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:40) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:183) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108) at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.UnsupportedOperationException: accept on org.hibernate.mapping.Any([org.hibernate.mapping.Column(cmvSourceTable), org.hibernate.mapping.Col umn(cmvSourceSID)]) at org.hibernate.tool.hbm2x.visitor.DefaultValueVisitor.handle(DefaultValueVisitor.java:40) at org.hibernate.tool.hbm2x.visitor.DefaultValueVisitor.accept(DefaultValueVisitor.java:87) at org.hibernate.mapping.Any.accept(Any.java:67) at org.hibernate.tool.hbm2x.Cfg2HbmTool.getHibernateTypeName(Cfg2HbmTool.java:380) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at freemarker.ext.beans.BeansWrapper.invokeMethod(BeansWrapper.java:583) at freemarker.ext.beans.SimpleMethodModel.exec(SimpleMethodModel.java:113) ... 63 more [hibernatetool] An exception occurred while running exporter #2:hbm2doc (Generates html schema documentation) [hibernatetool] To get the full stack trace run ant with -verbose [hibernatetool] org.hibernate.tool.hbm2x.ExporterException: Error while processing template dot/entitygraph.dot.ftl [hibernatetool] freemarker.template.TemplateModelException: Method public java.lang.String org.hibernate.tool.hbm2x.Cfg2HbmTool.getHibernateTypeName(org.hiberna te.mapping.Property) threw an exception when invoked on org.hibernate.tool.hbm2x.Cfg2HbmTool@7348e [hibernatetool] java.lang.UnsupportedOperationException: accept on org.hibernate.mapping.Any([org.hibernate.mapping.Column(cmvSourceTable), org.hibernate.mappin g.Column(cmvSourceSID)]) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2890) Hibernate cannot wrap HSQLDB constraint violations exceptions

by Baptiste MATHUS (JIRA)

Hibernate cannot wrap HSQLDB constraint violations exceptions ------------------------------------------------------------- Key: HHH-2890 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2890 Project: Hibernate3 Issue Type: Sub-task Components: core Affects Versions: 3.2.1 Reporter: Baptiste MATHUS Priority: Minor Attachments: UnitTestConstraintBug.zip Since I can't attach a file to a bug that hasn't been logged by me. I'll create a sub-bug, since logging a bug was anyway something I planned to do when I created the testcase. In the attached zip, you'll find a project that has two entities: Customer and Invoice. An Invoice references a Customer. I show that trying to delete a Customer that's referenced by an invoice doesn't throw a ConstraintViolationException with HSQLDB (1.8.0.7 or 1.7.3.3 gives the same result). The testcase is in the test package. I hope this helps tackle the problem. Before logging a bug in the HSQL tracker, I'd really appreciate to have your opinion. Shoud I do it? FYI, I tested the very same code on Oracle, and the ConstraintViolationException is very well thrown... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

4
7
0 / 0

[Hibernate-JIRA] Created: (ANN-442) Support @GenericGenerators

by Emmanuel Bernard (JIRA)

Support @GenericGenerators -------------------------- Key: ANN-442 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-442 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Emmanuel Bernard Priority: Minor To support more than one generic generator in package-info.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-129) IndexedEmbedded for Collections Documentation

by Jay Bose (JIRA)

IndexedEmbedded for Collections Documentation --------------------------------------------- Key: HSEARCH-129 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-129 Project: Hibernate Search Issue Type: Improvement Reporter: Jay Bose I was wondering why a query like "parent.child.name:foo" was not working. After a few different searches I found this response -- http://forum.hibernate.org/viewtopic.php?p=2348475#2348475 It would be helpful if the current documentation described if and how associated objects (collections) should be indexed for certain queries. Also, should @ContainedIn AND @IndexedEmbedded be used for one collection? See below. @ContainedIn @IndexedEmbedded(depth = 1) Set<Keyword> keywords; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-144) add option to keep indexer running till finished.

by Jason Eacott (JIRA)

add option to keep indexer running till finished. ------------------------------------------------- Key: HSEARCH-144 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-144 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Jason Eacott Hi all, I've just installed and got running hibernate search - very cool! But a very minor enancement would help a lot I think, for those of us still in testing mode and not using the jms option yet. It would be very handy if there was a config option for the async executorService to stay up and complete its tasks after the app itself has been shutdown. In BatchedQueueingProcessor finalize just need to add something like this line after the executorService.shutdown();( if its set to wait in the config somewhere of course), or even better replace the params here with user defined entries from config. executorService.awaitTermination(Long.MAX_VALUE, TimeUnit.SECONDS ); The only other feature I'd like is the capability to use Spring jms instead of the jboss one out of the box. :) Great product. Cheers Jason. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-127) Wrong prefix for worker configurations.

by Jay Bose (JIRA)

Wrong prefix for worker configurations. --------------------------------------- Key: HSEARCH-127 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-127 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.0.0.GA Environment: online here - http://www.hibernate.org/hib_docs/search/reference/en/html/search-configu... Reporter: Jay Bose Priority: Minor In Table 3.2. worker configurations are all prefixed with "org.hibernate.", when it should be "hibernate.search." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-52) Hibernate Shards not applying setMaxResults as a SQL LIMIT

by Max Ross (JIRA)

Hibernate Shards not applying setMaxResults as a SQL LIMIT ---------------------------------------------------------- Key: HSHARDS-52 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-52 Project: Hibernate Shards Issue Type: Bug Components: engine Reporter: Max Ross Assignee: Max Ross Fix For: 3.0.0 http://forum.hibernate.org/viewtopic.php?p=2374359&sid=b337277456949beac5... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-136) CachingWrapperFilter does not cache

by Tobias Hill (JIRA)

CachingWrapperFilter does not cache ------------------------------------ Key: HSEARCH-136 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-136 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Tobias Hill See http://forum.hibernate.org/viewtopic.php?p=2369054#2369054 The CachingWrapperFilter uses the reader instance as a key for the caching. In HibernateSearch readers seems to be wrapped into a MultiReader which by itself is new each time and thus defeat the cache purpose. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-147) Allow projection of Lucene DocId

by Christian Wiedmann (JIRA)

Allow projection of Lucene DocId -------------------------------- Key: HSEARCH-147 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-147 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.0.0.GA Reporter: Christian Wiedmann Priority: Minor It would be nice if the Lucene docid could be projected from a query so that TokenSources.getAnyTokenStream(IndexReader reader, int docId, String field, Analyzer analyzer) can be used. This function has the advantage that it extracts the token stream from Lucene without reparsing if it is able to. If it is unable, it will reparse the stored field with the given analyzer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-125) Add support for fields declared by interface or unmapped superclass

by Igor Stroh (JIRA)

Add support for fields declared by interface or unmapped superclass ------------------------------------------------------------------- Key: HSEARCH-125 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-125 Project: Hibernate Search Issue Type: Improvement Components: engine, mapping Affects Versions: 3.0.0.GA Reporter: Igor Stroh Priority: Minor Attachments: IndexedTarget.patch If an @IndexedEmbedded field is delcared by an interface or a unmapped superclass, there is no way hibernate-search can resolve the concrete class (compare to org.hibernate.annotations.Target or the targetEntity parameter for @*To* annotations). The attached patch solves this issue by introducing a IndexedTarget annotation which, much like @Target, expects the mapped class as its single parameter. See test/org/hibernate/search/test/embedded/ changes for a simple example. This issue was first exmplained in http://forum.hibernate.org/viewtopic.php?p=2366118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-130) Should provide better log infos (on the indexBase parameter for the FSDirectoryProvider)

by Eric Perrocheau (JIRA)

Should provide better log infos (on the indexBase parameter for the FSDirectoryProvider) ---------------------------------------------------------------------------------------- Key: HSEARCH-130 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-130 Project: Hibernate Search Issue Type: Improvement Components: directory provider Affects Versions: 3.0.0.GA Reporter: Eric Perrocheau Priority: Minor When tracking bugs due to invalid directories names for the FSDirectoryProvider, it could be nice if the logs did inform more on Hibernate Search behaviour, or help highlight some problem. E.g., if the indexes already exist on disk, under windows vista, and we provide the directory name with erroneous trailing spaces in the configuration file : Hibernate Search run half well : the only problem is that it clears the old indexes on initializing the FSDirectoryProvider since it didn't find the directory with the trailing spaces. After that, it doesn't seem to mind the wrong directory name since it finds and uses the good one. Is suppose we could expect Hibernate Search to tell that something is happening and why, in fact, without having to go in the code with the debugger to find that the trailing spaces are sometimes a problem and sometimes not. (this improvement was asked for on http://forum.hibernate.org/viewtopic.php?t=980567 ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-126) Better diagnostic when Search index directory cannot be opened

by Ian (JIRA)

Better diagnostic when Search index directory cannot be opened -------------------------------------------------------------- Key: HSEARCH-126 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-126 Project: Hibernate Search Issue Type: Patch Affects Versions: 3.1.0 Environment: Found in version deployed inside JBoss-Seam 2.0.0.CR2, but affects more Reporter: Ian Priority: Minor Attachments: DirectoryProviderHelper.diff When Search cannot create the index directory, the message in the Exception thrown by o.h.s.util.DirectoryProviderHelper.java contains the path as entered by the original user; it is often the case that this will be deployed inside an application server and the user will not know the correct path that is in need of permissions repair because of the way e.g., JBoss-AS creates randomly named subdirectories under e.g., server/default/deploy. This just changes the message to include the full path if the user gave an absolute path. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (ANN-693) org.hibernate.engine.query.sql.NativeSQLQueryScalarReturn not serializable

by Eugeniusz Neugebauer (JIRA)

org.hibernate.engine.query.sql.NativeSQLQueryScalarReturn not serializable -------------------------------------------------------------------------- Key: ANN-693 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-693 Project: Hibernate Annotations Issue Type: Bug Environment: jboss 4.2.2, HB 3.2.5 Reporter: Eugeniusz Neugebauer In my domain class I've NamedNativeQuery: @SqlResultSetMappings({@SqlResultSetMapping(name = "uir_suma_zbiorow_result", columns = @ColumnResult(name = "result"))}) @NamedNativeQueries({@NamedNativeQuery(name = "uir.uir_suma_zbiorow", query = "select uir_suma_zbiorow(:var1, :var2, :var3) as result", resultSetMapping = "uir_suma_zbiorow_result")}) During build session factory on jboss i have Exception: Caused by: javax.naming.CommunicationException [Root exception is java.io.NotSerializableException: org.hibernate.engine.query.sql.NativeSQLQueryScalarReturn] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:618) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:552) at org.jboss.util.naming.Util.bind(Util.java:102) at org.jboss.util.naming.Util.bind(Util.java:89) at pl.computerland.syriusz.std.hibernate.jmx.Hibernate2.bind(Hibernate2.java:429) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3084) DialectFactory.java doesn't map the IngresDialect

by Michael Leo (JIRA)

DialectFactory.java doesn't map the IngresDialect ------------------------------------------------- Key: HHH-3084 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3084 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0.ga, 3.2.0.cr5, 3.2.0.cr4, 3.2.0.cr3, 3.2.0.cr2, 3.2.0 cr1, 3.1.3, 3.2.0.alpha2, 3.2.0.alpha1, 3.1.2, 3.1.1, 3.1, 3.1 rc3, 3.1 rc2, 3.1 rc 1, 3.1 beta 2, 3.1 beta 1, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0 final, 3.0 rc 1, 3.0 beta 4, 3.0 beta 3, 3.0 beta 2, 3.0 beta 1, 3.0 alpha Environment: Hibernate 3.x and frameworks based on the Spring Framework, like Grails Reporter: Michael Leo Attachments: DialectFactory.java.patch Although Hibernate ships with an Ingres dialect org.hibernate.dialect.IngresDialect it can't be found by the dialect factory org.hibernate.dialect.DialectFactory Although most tools can be forced to use the proper dialect, there is a circumstance in Grails where there is no way to specify the correct Hibernate dialect for a custom data source. The patch is pretty straightforward. I've attached the output of "svn diff" from the root of the latest branch. Hope this makes sense, Mike Leo $ svn diff Index: src/org/hibernate/dialect/DialectFactory.java =================================================================== --- src/org/hibernate/dialect/DialectFactory.java (revision 14289) +++ src/org/hibernate/dialect/DialectFactory.java (working copy) @@ -112,6 +112,9 @@ private static final Map MAPPERS = new HashMap(); static { // TODO : this is the stuff it'd be nice to move to a properties file or some other easily user-editable place + MAPPERS.put( "Ingres", new VersionInsensitiveMapper( "org.hibernate.dialect.IngresDialect" ) ); + MAPPERS.put( "ingres", new VersionInsensitiveMapper( "org.hibernate.dialect.IngresDialect" ) ); + MAPPERS.put( "INGRES", new VersionInsensitiveMapper( "org.hibernate.dialect.IngresDialect" ) ); MAPPERS.put( "HSQL Database Engine", new VersionInsensitiveMapper( "org.hibernate.dialect.HSQLDialect" ) ); MAPPERS.put( "DB2/NT", new VersionInsensitiveMapper( "org.hibernate.dialect.DB2Dialect" ) ); MAPPERS.put( "DB2/LINUX", new VersionInsensitiveMapper( "org.hibernate.dialect.DB2Dialect" ) ); $ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2957) ActionQueue Insertion sort performance degrades exponentially

by Jay Erb (JIRA)

ActionQueue Insertion sort performance degrades exponentially ------------------------------------------------------------- Key: HHH-2957 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2957 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Reporter: Jay Erb Attachments: ActionQueue.java, NewInsertActionSorter.java The algorithm for sorting entity insertions performs poorly for when flushing large numbers of entity insertions. There are a few reasons for this: 1. The sort used linear searches over lists which required nested looping. 2. ArrayLists were used to hold the insertion events. ArrayLists give good performance for looping but they have a couple of significant drawbacks: a. Whenever a new item is added to the list, the list is rebuilt with the new size, which causes another loop over all the entries in the list. b. Since it is an array, a contiguous block of memory must be found to hold the array. As the array get large, it gets harder and harder to find a contiguous block large enough. This causes the garbage collector to be run more often, which obviously reduces performance again. I changed the algorithm so that the product of the sort is exactly the same. The difference is that I used hashes for searches and LinkedLists for storing the insertions. The performance is linear. Attached are my changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
13
0 / 0

[Hibernate-JIRA] Commented: (ANN-401) @OrderBy does not work with inherited properties

by Dave Whittaker (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-401?page=co... ] Dave Whittaker commented on ANN-401: ------------------------------------ I'm curious as to why this would be so difficult. Could one not just check the metadata for the target object to see where the order by property is within the class hierarchy and then do an additional join to the table that represents the targets superclass? Ok, that was clearer in my head than it sounds when I re-read it. Basically, using the example above (with joined inheritance) why can't the location of propertyForOrderBy by determined to be class A (I'm assuming Hibernate already has this information available), which could result in the table for class A being joined during the query using the primary keys of A and B, then the order by would simply have to reference the table for A. Or am I completely off here....... > @OrderBy does not work with inherited properties > ------------------------------------------------ > > Key: ANN-401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-401 > Project: Hibernate Annotations > Issue Type: Bug > Components: binder > Affects Versions: 3.2.0.cr1 > Environment: Hibernate 3.2, MySql 4, Windows XP > Reporter: Guido Laures > > Using an @OrderBy with an inherited property produces an SQL Exception. > Example: > @Entity > class Base { > ... > public int getPropertyForOrderBy(){ return propertytoOrderBy; } > ... > } > @Entity > @PrimaryKeyJoinColumn(name="a_id") > class A extends Base { > ... > } > @Entity > @PrimaryKeyJoinColumn(name="b_id") > class B extends Base { > ... > @OneToMany(mappedBy = "someProp", cascade = { CascadeType.ALL }) > @OrderBy("propertyToOrderBy") > public Set<A> getASet() { > return this.aSet; > } > ... > } > Thus, if A references a set of Bs and wants it to be ordered by a property of B's base class Base it crashes. The generated SQL string tries to find the property from the base class in the table of the inerited class (A) which fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1956) Interceptor.afterTransactionCompletion not called with JTATransaction (CacheSynchronization.hibernateTransaction not set)

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1956?page=c... ] Steve Ebersole commented on HHH-1956: ------------------------------------- qualification of "whenever we register a synch should be a viable trigger event"... specifically talking about the code (currently) in org.hibernate.jdbc.JDBCContext#registerSynchronizationIfPossible (~ line 169) where we register the JTA synch: tx.registerSynchronization( new CacheSynchronization(owner, this, tx, null) ); isTransactionCallbackRegistered = true; log.debug("successfully registered Synchronization"); return true; (note that the null param to the CacheSynchronization ctor here is supposed to be the hibernateTransaction...) becoming something like: Transaction hibernateTransaction = this.hibernateTransaction; if ( hibernateTransaction == null ) { hibernateTransaction = owner.getFactory().getSettings().getTransactionFactory().createTransaction( this, owner ); } tx.registerSynchronization( new CacheSynchronization(owner, this, tx, hibernateTransaction) ); isTransactionCallbackRegistered = true; if ( this.hibernateTransaction == null ) { this.hibernateTransaction = hibernateTransaction; } log.debug("successfully registered Synchronization"); return true; The difference being that the hibernateTransaction is no longer null in these JTA scenarios we are discussing... > Interceptor.afterTransactionCompletion not called with JTATransaction (CacheSynchronization.hibernateTransaction not set) > ------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1956 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1956 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Environment: JBoss 4.0.3SP1 under Windows XP > Reporter: Eric Sword > Assignee: Steve Ebersole > Fix For: 3.2.6, 3.3 > > > interceptor.afterTransactionCompletion should be invoked in SessionImpl.afterTransactionCompletion, but it is only called if the tx parameter is not null. When running under a JTA environment, that parameter will always be null. This is the stack which leads to the call (line numbers are from v3.1.2 code): > org.hibernate.impl.SessionImpl.afterTransactionCompletion(boolean, org.hibernate.Transaction) line: 442 > org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(boolean, org.hibernate.Transaction) line: 205 > org.hibernate.transaction.CacheSynchronization.afterCompletion(int) line: 85 > org.jboss.tm.TransactionImpl.doAfterCompletion() line: 1508 > org.jboss.tm.TransactionImpl.completeTransaction() line: 1180 > org.jboss.tm.TransactionImpl.commit() line: 359 > org.jboss.tm.TxManager.commit() line: 224 > org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit() line: 126 > org.hibernate.transaction.JTATransaction.commit() line: 146 > The problem is that the hibernateTransaction member variable of the CacheSynchronization object is never set. Here is the call stack for how that object is created: > org.hibernate.transaction.CacheSynchronization.<init>(org.hibernate.transaction.TransactionFactory$Context, org.hibernate.jdbc.JDBCContext, javax.transaction.Transaction, org.hibernate.Transaction) line: 34 > org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible() line: 149 > org.hibernate.transaction.JTATransaction.begin() line: 102 > org.hibernate.impl.SessionImpl.beginTransaction() line: 1309 > com.osc.util.hibernate.HibernateManager.getSession(org.hibernate.Interceptor) line: 204 > You can see in the JDBCContext.registerSynchronizationIfPossible() method that the parameter to set the transaction is always null, even though the JDBCContext object does have a reference to the hibernateTransaction at that point. The CacheSynchronization only uses that reference for beforeTransactionCompletion and afterTransactionCompletion calls. The beforeTransactionCompletion works because the SessionImpl.beforeTransactionCompletion call doesn't check if the tx is null, while the afterTransactionCompletion does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1956) Interceptor.afterTransactionCompletion not called with JTATransaction (CacheSynchronization.hibernateTransaction not set)

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1956?page=c... ] Steve Ebersole updated HHH-1956: -------------------------------- Assignee: Steve Ebersole Fix Version/s: 3.3 3.2.6 There seem to be 2 approaches to solving this: 1) skip the checks about null hibernateTransaction 2) make sure a hibernateTransaction is present in these scenarios (whenever we register a synch should be a viable trigger event). > Interceptor.afterTransactionCompletion not called with JTATransaction (CacheSynchronization.hibernateTransaction not set) > ------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1956 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1956 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Environment: JBoss 4.0.3SP1 under Windows XP > Reporter: Eric Sword > Assignee: Steve Ebersole > Fix For: 3.2.6, 3.3 > > > interceptor.afterTransactionCompletion should be invoked in SessionImpl.afterTransactionCompletion, but it is only called if the tx parameter is not null. When running under a JTA environment, that parameter will always be null. This is the stack which leads to the call (line numbers are from v3.1.2 code): > org.hibernate.impl.SessionImpl.afterTransactionCompletion(boolean, org.hibernate.Transaction) line: 442 > org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(boolean, org.hibernate.Transaction) line: 205 > org.hibernate.transaction.CacheSynchronization.afterCompletion(int) line: 85 > org.jboss.tm.TransactionImpl.doAfterCompletion() line: 1508 > org.jboss.tm.TransactionImpl.completeTransaction() line: 1180 > org.jboss.tm.TransactionImpl.commit() line: 359 > org.jboss.tm.TxManager.commit() line: 224 > org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit() line: 126 > org.hibernate.transaction.JTATransaction.commit() line: 146 > The problem is that the hibernateTransaction member variable of the CacheSynchronization object is never set. Here is the call stack for how that object is created: > org.hibernate.transaction.CacheSynchronization.<init>(org.hibernate.transaction.TransactionFactory$Context, org.hibernate.jdbc.JDBCContext, javax.transaction.Transaction, org.hibernate.Transaction) line: 34 > org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible() line: 149 > org.hibernate.transaction.JTATransaction.begin() line: 102 > org.hibernate.impl.SessionImpl.beginTransaction() line: 1309 > com.osc.util.hibernate.HibernateManager.getSession(org.hibernate.Interceptor) line: 204 > You can see in the JDBCContext.registerSynchronizationIfPossible() method that the parameter to set the transaction is always null, even though the JDBCContext object does have a reference to the hibernateTransaction at that point. The CacheSynchronization only uses that reference for beforeTransactionCompletion and afterTransactionCompletion calls. The beforeTransactionCompletion works because the SessionImpl.beforeTransactionCompletion call doesn't check if the tx is null, while the afterTransactionCompletion does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3074) Remove lib/jdbc2_0-stdext.jar since it is no longer needed

by Gail Badner (JIRA)

Remove lib/jdbc2_0-stdext.jar since it is no longer needed ---------------------------------------------------------- Key: HHH-3074 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3074 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.6 lib/jdbc2_0-stdext.jar is only needed for JDK versions prior to 1.4. Since the hibernate core build targets Java 1.4, this jar can be removed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3089) Detailed explanation on how to call Oracle stored procedure from hibernate mapping file.

by Yamini Seshadri (JIRA)

Detailed explanation on how to call Oracle stored procedure from hibernate mapping file. ----------------------------------------------------------------------------------------- Key: HHH-3089 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3089 Project: Hibernate3 Issue Type: Task Reporter: Yamini Seshadri Please help me with a detailed code snippet of how to call Oracle stored procedure from hibernate mapping file. The procedure returns one OUT Parameter. Also pls help me in processing the OUT parameter in java file once called from hibernate mapping file. Need to immediate help. Post ur replies to: yamini.v.s(a)cognizant.com Thanks in advance Yamini -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3088) Collection "remove" events don't contain removed collection when detached entity is updated with a null collection

by Gail Badner (JIRA)

Collection "remove" events don't contain removed collection when detached entity is updated with a null collection ------------------------------------------------------------------------------------------------------------------ Key: HHH-3088 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3088 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner When a detached entity is updated with a null collection using Session.update(), the collection is deleted without being loaded. For this reason, pre- and post- collection-remove events contain a null collection, instead of the collection that was removed. A "FailureExpected" test case was added to org.hibernate.test.event.collection.BrokenCollectionEventTest, testUpdateDetachedParentNoChildrenToNullFailureExpected, which fails because the collection in the pre- and post-collection-remove events are expected to contain the collection being removed. Another test case, testUpdateDetachedParentOneChildToNullFailureExpected, is commented out since it fails for the same reason. When this is fixed, both test case should be moved to org.hibernate.test.event.collection.AbstractCollectionEventTest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3087) No collection create eventst when collection is set to null

by Gail Badner (JIRA)

No collection create eventst when collection is set to null ----------------------------------------------------------- Key: HHH-3087 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3087 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner When an entity is saved or updated with a null collection, pre- and post-collection-recreate events are not generated. These events are generated when saving or updating an entity with an empty collection. Two "FailureExpected" tests have been added to org.hibernate.test.event.collection.BrokenCollectionEventTest:, which fail because the test case expects pre- and post-collection-recreate events to be generated: - testSaveParentNullChildrenFailureExpected: a parent entity with an empty collection is saved with a null collection - testUpdateParentNoChildrenToNullFailureExpected: a parent entity that has been persisted with a non-null collection is updated with a null collection. The following two tests have been also been added, but are commented out because they fail for the same reason as testUpdateParentNoChildrenToNullFailureExpected: - testUpdateParentOneChildToNullFailureExpected: a parent entity that has been persisted with an non-empty collection is saved with a null collection - testUpdateMergedParentOneChildToNullFailureExpected: a detached parent entity that has been persisted with a non-empty collection is merged into a session with a null collection When this bug is fixed, all 4 tests should be moved to org.hibernate.test.event.collection.AbstractCollectionEventTest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2616) No event is fired on Collection recreate/remove/update action

by Emmanuel Bernard (JIRA)

No event is fired on Collection recreate/remove/update action ------------------------------------------------------------- Key: HHH-2616 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2616 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4 Reporter: Emmanuel Bernard There is no way today to know if a collection has been updated (in the generic sense of it) managedEntity.getCollection().add(object) fires no event. Seems to me that it should fire Pre/PostUpdateEvent. Because of PostUpdateEvent signature we might need a PostUpdateCollectionEvent (Update meaning Update/Create/Delete) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3086) Remove jdbc2_0-stdext.jar (unnecessary library)

by Steve Ebersole (JIRA)

Remove jdbc2_0-stdext.jar (unnecessary library) ----------------------------------------------- Key: HHH-3086 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3086 Project: Hibernate3 Issue Type: Task Components: core Affects Versions: 3.2.5 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.6 move to jdk 1.4 made this unnecessary, but it was never removed... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3085) Remove connector.jar (unnecessary library)

by Steve Ebersole (JIRA)

Remove connector.jar (unnecessary library) ------------------------------------------ Key: HHH-3085 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3085 Project: Hibernate3 Issue Type: Task Components: core Affects Versions: 3.2.5 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.6 Clean up connector.jar; left over from (now removed) JCA features. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-50) Bug in annotation example coe

by Max Ross (JIRA)

Bug in annotation example coe ----------------------------- Key: HSHARDS-50 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-50 Project: Hibernate Shards Issue Type: Bug Components: documentation Affects Versions: 3.0.0.Beta2 Reporter: Max Ross Assignee: Max Ross Priority: Trivial Fix For: 3.0.0 In the Annotation example in the documentation, the type of the field annotated with @Id is Integer but we're using ShardedUUIDGenerator, which returns BigInteger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-12) Check Validator

by Anderson Souza (JIRA)

Check Validator --------------- Key: HV-12 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-12 Project: Hibernate Validator Issue Type: Patch Components: validators Affects Versions: 3.0.0.ga Reporter: Anderson Souza Attachments: patch.zip It's a new validator with the same behavior of database check constraints. I think it will be very useful. I had to apply a small change to the DefaultMessageInterpolator class, just to permit the array values to be interpolated on the generated message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2588) Incorrect database updates with "generated" fields in record

by Frits Jalvingh (JIRA)

Incorrect database updates with "generated" fields in record ------------------------------------------------------------ Key: HHH-2588 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2588 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3, 3.2.0.ga Environment: Tested with Hibernate 3.2.3 and 3.2.0GA, Oracle 10gR2, Linux, Java 5. Reporter: Frits Jalvingh I have a single POJO (UserGroup) which is based on a superclass which defines a number of properties as @Generated(GenerationTime.INSERT); amongst others tcn and ros_id. These properties are defined as "not null" in the database, and are filled in by an insert database trigger. When I create a new instance and do this: -------------------- Transaction tr = getSession().beginTransaction(); UserGroup ug = new UserGroup(); ug.setType(UserGroupType.PLN); ug.setName(name); ug.setDescription(desc); getSession().save(ug); // persist() exhibits the same problem... ug.setGroupEmail("jaja(a)nono.com"); tr.commit(); -------------------- I get a database exception: ORA-01407: cannot update ("TEST"."CRM_GROUPS"."ROS_ID") to NULL When I look at the persister's logging I see something very wrong happening: -------------------- DEBUG - commit DEBUG - automatically flushing session DEBUG - flushing session DEBUG - processing flush-time cascades DEBUG - dirty checking collections DEBUG - Flushing entities and processing referenced collections DEBUG - nl.itris.viewpoint.db.crm.UserGroup.groupEmail is dirty DEBUG - nl.itris.viewpoint.db.crm.UserGroup.memberMutable is dirty DEBUG - Updating entity: [nl.itris.viewpoint.db.crm.UserGroup#1150000159] DEBUG - nl.itris.viewpoint.db.crm.UserGroup.groupEmail is dirty DEBUG - nl.itris.viewpoint.db.crm.UserGroup.memberMutable is dirty DEBUG - Collection found: [nl.itris.viewpoint.db.crm.UserGroup.memberList#1150000159], was: [<unreferenced>] (initialized) DEBUG - Processing unreferenced collections DEBUG - Scheduling collection removes/(re)creates/updates DEBUG - Flushed: 1 insertions, 1 updates, 0 deletions to 1 objects DEBUG - Flushed: 1 (re)creations, 0 updates, 0 removals to 1 collections DEBUG - listing entities: DEBUG - nl.itris.viewpoint.db.crm.UserGroup{groupEmail=jal(a)etc.to, memberList=[], type=PLN, tcn=null, logTime=null, logModule=null, id=1150000159, organisationId=null, groupLeader=null, description=test2, memberMutable=null, logDate=null, name=test2, logUser=null} DEBUG - executing flush DEBUG - registering flush begin DEBUG - Inserting entity: [nl.itris.viewpoint.db.crm.UserGroup#1150000159] DEBUG - about to open PreparedStatement (open PreparedStatements: 0, globally: 0) DEBUG - insert into CRM_GROUPS (CGP_DESCRIPTION, CGP_GROUPEMAIL, CST_ID, CGP_MEMBER_MUTABLE, CGP_NAME, CGP_TYPE, CGP_ID) values (?, ?, ?, ?, ?, ?, ?) DEBUG - preparing statement DEBUG - Dehydrating entity: [nl.itris.viewpoint.db.crm.UserGroup#1150000159] DEBUG - binding 'test2' to parameter: 1 DEBUG - binding null to parameter: 2 DEBUG - binding null to parameter: 3 DEBUG - binding 'test2' to parameter: 5 DEBUG - Binding 'PLN' to parameter: 6 DEBUG - binding '1150000159' to parameter: 7 DEBUG - Executing batch size: 1 DEBUG - success of batch update unknown: 0 DEBUG - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) DEBUG - closing statement DEBUG - about to open PreparedStatement (open PreparedStatements: 0, globally: 0) DEBUG - select usergroup_.LOG_DATE as LOG2_74_, usergroup_.LOG_MODULE as LOG3_74_, usergroup_.LOG_TIME as LOG4_74_, usergroup_.LOG_USER as LOG5_74_, usergroup_.TCN as TCN74_, usergroup_.ROS_ID as ROS7_74_ from CRM_GROUPS usergroup_ where usergroup_.CGP_ID=? DEBUG - preparing statement DEBUG - binding '1150000159' to parameter: 1 DEBUG - about to open ResultSet (open ResultSets: 0, globally: 0) DEBUG - returning '2007-04-26 00:00:00' as column: LOG2_74_ DEBUG - returning null as column: LOG3_74_ DEBUG - returning '14:28:04' as column: LOG4_74_ DEBUG - returning 'VPC' as column: LOG5_74_ DEBUG - returning '310525020' as column: TCN74_ DEBUG - returning '1500' as column: ROS7_74_ DEBUG - about to close ResultSet (open ResultSets: 1, globally: 1) DEBUG - Updating entity: [nl.itris.viewpoint.db.crm.UserGroup#1150000159] DEBUG - about to open PreparedStatement (open PreparedStatements: 1, globally: 1) DEBUG - update CRM_GROUPS set TCN=?, ROS_ID=?, CGP_DESCRIPTION=?, CGP_GROUPEMAIL=?, CST_ID=?, CGP_MEMBER_MUTABLE=?, CGP_NAME=?, CGP_TYPE=? where CGP_ID=? DEBUG - preparing statement DEBUG - Dehydrating entity: [nl.itris.viewpoint.db.crm.UserGroup#1150000159] DEBUG - binding null to parameter: 1 DEBUG - binding null to parameter: 2 DEBUG - binding 'test2' to parameter: 3 DEBUG - binding 'jal(a)etc.to' to parameter: 4 DEBUG - binding null to parameter: 5 DEBUG - binding 'test2' to parameter: 7 DEBUG - Binding 'PLN' to parameter: 8 DEBUG - binding '1150000159' to parameter: 9 DEBUG - Executing batch size: 1 DEBUG - about to close PreparedStatement (open PreparedStatements: 2, globally: 2) DEBUG - closing statement DEBUG - Could not execute JDBC batch update [update CRM_GROUPS set TCN=?, ROS_ID=?, CGP_DESCRIPTION=?, CGP_GROUPEMAIL=?, CST_ID=?, CGP_MEMBER_MUTABLE=?, CGP_NAME=?, CGP_TYPE=? where CGP_ID=?] to.etc.dbpool.BetterSQLException: java.sql.BatchUpdateException: ORA-01407: cannot update ("VIEWPOINT"."CRM_GROUPS"."ROS_ID") to NULL SQL: update CRM_GROUPS set TCN=?, ROS_ID=?, CGP_DESCRIPTION=?, CGP_GROUPEMAIL=?, CST_ID=?, CGP_MEMBER_MUTABLE=?, CGP_NAME=?, CGP_TYPE=? where CGP_ID=? Parameters: #1:[null] #2:[null] #3:java.lang.String:test2 #4:java.lang.String:jal@etc.to #5:[null] #6:java.lang.String:N #7:java.lang.String:test2 #8:java.lang.String:PLN #9:java.lang.Long:1150000159 at to.etc.dbpool.PreparedStatementProxy.wrap(PreparedStatementProxy.java:68) at to.etc.dbpool.StatementProxy.executeBatch(StatementProxy.java:176) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246) at org.hibernate.persister.entity.AbstractEntityPersister.processGeneratedProperties(AbstractEntityPersister.java:3691) at org.hibernate.persister.entity.AbstractEntityPersister.processUpdateGeneratedProperties(AbstractEntityPersister.java:3680) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:124) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at nl.itris.moca.ajax.Planner.updatePlanGroup(Planner.java:1717) ---------------------------------- Hibernate starts by inserting the new record correctly, and then reselects the inserted record to retrieve the changed fields correctly. But after that it does an update of that record with stale data: it sets all of the generated fields it *has* read to null, and updates the groupEmail field which for some reason was not present in the insert!? It looks like multiple versions of the same records are maintained in some way?? The problem is triggered by the existence of the "save" call *followed by* another change to the record. But the same problem occurs when other things cause an intermediary update, for instance when trying to save the data in a collection parented by UserGroup. Because this problem also occurs when I add/change elements in the UserGroup's associated GroupMember one-to-many association I am effectively unable to store a group with it's members in one transaction! In addition I noticed that the persist() call seems to check defined constraints on the record at the time persist() is called instead of the time that it gets commited. This means it can only be called when the pojo is complete which looks odd to me? I sort of understand this for save() as that is required to return the primary key but I do not understand why this is needed for persist... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3083) Incorrect delete handling

by Krashan Brahmanjara (JIRA)

Incorrect delete handling ------------------------- Key: HHH-3083 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3083 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: 3.2.5.ga Reporter: Krashan Brahmanjara When user try to delete not existing row from database see long exception message. Real databases like Informix report status=0 and don't report any error in this case and users probably expect the same from Hibernate. I think that should be rather NotFoundException than org.hibernate.StaleStateException etc. I see this error also when hibernate.jdbc.batch_size is 0 a Current exception trace in this case 2008-01-24 15:48:43 org.hibernate.event.def.AbstractFlushingEventListener performExecutions SEVERE: Could not synchronize database state with session org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1 at org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched(Expectations.java:61) at org.hibernate.jdbc.Expectations$BasicExpectation.verifyOutcome(Expectations.java:46) at org.hibernate.jdbc.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:24) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2520) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2697) at org.hibernate.action.EntityDeleteAction.execute(EntityDeleteAction.java:74) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:234) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:146) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2384) Patch for using case-expression("case ... when ... end") in aggregate functions

by Florian Rock (JIRA)

Patch for using case-expression("case ... when ... end") in aggregate functions ------------------------------------------------------------------------------- Key: HHH-2384 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2384 Project: Hibernate3 Type: Patch Components: query-hql Versions: 3.2.2 Reporter: Florian Rock Priority: Minor Attachments: aggrcasehql.patch using a case-expression in aggregate functions causes a QuerySyntaxException.. ie.: "count(case when fubar > 0 then 1 else null end)" i changed some things in the grammar to solve this, patch is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1033) org.hibernate.console.HibernateConsoleRuntimeException: Could not compute classpath

by Chris (JIRA)

org.hibernate.console.HibernateConsoleRuntimeException: Could not compute classpath ----------------------------------------------------------------------------------- Key: HBX-1033 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1033 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2.0.GA Environment: Hibernate 3.2, MySql 5/0, Eclipse for Java EE Developers( Europa ) Build id: M20070921-1145 Reporter: Chris After I create a "Hibernate Console Configuration" using the wizard I get the following error in the eclipse error log. eclipse.buildId=M20070921-1145 java.version=1.5.0_14 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 Error Fri Jan 11 14:33:38 EST 2008 org.hibernate.console.HibernateConsoleRuntimeException: Could not compute classpath Folowed by lots of org.hibernate.MappingException because it can't find classes detailed in the mapping files. I checked the box to include the projects classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
16
0 / 0

[Hibernate-JIRA] Commented: (HHH-468) MysqlDialect incorrectly maps java.lang.Boolean to SQL BIT

by Lieven Doclo (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-468?page=co... ] Lieven Doclo commented on HHH-468: ---------------------------------- To bring this issue back to life: Can't we just map BIT to tinyint(1) in the MySQL dialect. This seems okay for all MySQL dialects (MyISAM and InnoDB). One of the problems with bit in MySQL is that standard it's not show in a MySQL console. For example: "select bitField from testTable" = field values not shown in console. You have to use "select BIT(bitField) from testTable" or "select bitField+0 from testTable" to show the values. When using tinyint(1), you don't encounter this problem. So please fix this. > MysqlDialect incorrectly maps java.lang.Boolean to SQL BIT > ---------------------------------------------------------- > > Key: HHH-468 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-468 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.0.3 > Environment: Hibernate 3.0, MySQL. > Reporter: Mark Matthews > Assignee: Scott Marlow > > I didn't track down how java.lang.Boolean gets mapped to Types.BIT in hibernate, but you probably _don't_ want to map to "bit" like you do in MysqlDialect. > "bit", according to SQL99 (it's not in the core standard, and the type was actually dropped for sql2k3) is a bitfield, not a boolean value. You can of course define a bit(1), but it is technically more correct for java.lang.Boolean to map to a SQL BOOLEAN for MySQL since we support a BOOLEAN and a BIT. > It looks like the JDBC-3.0 guys ignored what the standard said, because in reality you'd want BIT to map to something like byte[], or java.util.BitSet if you were tracking how the SQL standard defines BIT. > I'm guessing you probably want to map to "boolean", which the JDBC driver will automagically convert for you, as it silently maps to TINYINT(1) on the server side. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3082) JPQL constructor_expression followed by an aggregate_expression in select_clause not supported

by Bob Tiernay (JIRA)

JPQL constructor_expression followed by an aggregate_expression in select_clause not supported ---------------------------------------------------------------------------------------------- Key: HHH-3082 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3082 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Reporter: Bob Tiernay >From the JPA spec: select_statement ::= select_clause from_clause [where_clause] [groupby_clause] [having_clause] [orderby_clause] select_clause ::= SELECT [DISTINCT] select_expression {, select_expression}* select_expression ::= single_valued_path_expression | aggregate_expression | identification_variable | OBJECT(identification_variable)| constructor_expression constructor_expression ::= NEW constructor_name( constructor_item {, constructor_item}*) Expanding the production rules confirms that select_clause should support both a constructor_expression and an aggregate_expression in sequence. For example: SELECT NEW package.DTO(e.f), COUNT(e) FROM Entity e WHERE ... However, doing so indicates a grammar error in the "," prior to the aggregate expression. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1725) lazy properties, events and collection xxx was not processed by flush exception and EJB3 incompatibility

by Geoffrey De Smet (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1725?page=c... ] Geoffrey De Smet commented on HHH-1725: --------------------------------------- Adrian: Emmanuel is a hibernate developer and he commented why. There's a heavy discussion going on at HHH-2763 and I hope that when that's fixed, my flush problems go away magically too (hey, I can hope, can't I?:) > lazy properties, events and collection xxx was not processed by flush exception and EJB3 incompatibility > -------------------------------------------------------------------------------------------------------- > > Key: HHH-1725 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1725 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.2.0.cr2 > Reporter: Tomasz Bech > > It is realted to anomaly: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1540 > 'When using custom event listeners, sometimes you mess with (and initialize) lazy collections by mistake, which causes CollectionEntry.postFlush(PersistentCollection) to throw an AssertionFailure' > It is questionable why AT ALL exception is raised in this case! > What is the most important: EJB3 spec is not prohibiting to check/read/ object involved in the event, so current implementation is agains EJB3 spec. > Events are often used for validation so it is quite probable that the lazy property (collection) has to be accessed - and when it is lazy and not initialized before the exception is raised. Why hibernate cannot treat it in nicer way and allow such actions. > One workaround is to not-use-lazy (very bad). > Second workaround: in the code outside flush (not in event) pre-initialize all lazy properties (in fact simulation of 'not-lazy). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-621) Unable to handle JOINED stragegy when the root entity id contains a @ManyToOne

by Emmanuel Bernard (JIRA)

Unable to handle JOINED stragegy when the root entity id contains a @ManyToOne ------------------------------------------------------------------------------ Key: ANN-621 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-621 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Priority: Minor Fix For: 3.3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1037) Reverse engineering doesn't match all tables

by Alessandro (JIRA)

Reverse engineering doesn't match all tables -------------------------------------------- Key: HBX-1037 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1037 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.0.GA Environment: Jdk 5.0, linux, Oracle and MySQL Reporter: Alessandro The table filter doesn't match all tables I want, either with the pattern ".*" or with the full name description of all tables. It seems the reverse engineering has problem with long name tables. Anyway, if I choose only some tables with the long name, the reverse engineering works... This debug seems to find all tables: {TABLE_SCHEM=GESTIONE_PROTOCOLLO_TEST, REMARKS=null, TABLE_CAT=null, TABLE_NAME=RISERVATEZZA, TABLE_TYPE=TABLE} but the "hbm.xml" files aren't generated. Some ideas? Thank you very much! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HV-26) Which version of Hibernate Annotations does ClassValidator depend on?

by Steven Devijver (JIRA)

Which version of Hibernate Annotations does ClassValidator depend on? --------------------------------------------------------------------- Key: HV-26 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-26 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 3.0.0.ga Reporter: Steven Devijver According to the Compatibility Matrix on the Hibernate website (http://www.hibernate.org/6.html) Hiberbate Validator 3.3.0 GA depends on Hibernate Annotations 3.3.x. The only 3.3.x release of Hibernate Annotations is 3.3.0 GA. However, the dependency in the compatibility matrix does not seem to be correct. When I load ClassValidator in my project I get this error: The type org.hibernate.annotations.common.reflection.ReflectionManager cannot be resolved. It is indirectly referenced from required .class files Version 3.3.0 GA of Hibernate Annotations however does not have the class org.hibernate.annotations.common.reflection.ReflectionManager. It does however contain org.hibernate.annotations.common.reflection.EJB3ReflectionManager. So, which version of Hibernate Annotations should be used with Hibernate Validator 3.0.0 GA? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

5
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3076) Can not create Table with Many to Many relationships

by Farooq Ahmad (JIRA)

Can not create Table with Many to Many relationships ---------------------------------------------------- Key: HHH-3076 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3076 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 HSQL DB for Unit Testing Hibernate Annotations with Spring Reporter: Farooq Ahmad Hi I am getting following error while using @ManytoMany relationships. Interesting thing is that my all unit tests are working fine. **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table ClueGiver add constraint FK7E948E28D7D12F96 foreign key (id) references Interactor **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table ClueGiver add constraint FK7E948E28D7D12F96 foreign key (id) references Interactor] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table Emoticon add constraint FK49B622A68A1F97CD foreign key (AVAT_ID) references Avatar **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table Emoticon add constraint FK49B622A68A1F97CD foreign key (AVAT_ID) references Avatar] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table Interactor add constraint FK1744CAB9E1ED9A42 foreign key (information_fk) references Information **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table Interactor add constraint FK1744CAB9E1ED9A42 foreign key (information_fk) references Information] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table Inventory_InventoryItem add constraint FK23935CAC15C312C3 foreign key (inventoryItems_id) references InventoryItem **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table Inventory_InventoryItem add constraint FK23935CAC15C312C3 foreign key (inventoryItems_id) references InventoryItem] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table Inventory_InventoryItem add constraint FK23935CACE9836C18 foreign key (Inventory_id) references Inventory **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table Inventory_InventoryItem add constraint FK23935CACE9836C18 foreign key (Inventory_id) references Inventory] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestAcceptor add constraint FK29C94BCDD7D12F96 foreign key (id) references Interactor **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestAcceptor add constraint FK29C94BCDD7D12F96 foreign key (id) references Interactor] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestAcceptor_Reward add constraint FK4CB17C01BC814F98 foreign key (QuestAcceptor_id) references QuestAcceptor **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestAcceptor_Reward add constraint FK4CB17C01BC814F98 foreign key (QuestAcceptor_id) references QuestAcceptor] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestAcceptor_Reward add constraint FK4CB17C0130F29C27 foreign key (rewards_id) references Reward **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestAcceptor_Reward add constraint FK4CB17C0130F29C27 foreign key (rewards_id) references Reward] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestGiver add constraint FK97D307DFD7D12F96 foreign key (id) references Interactor **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestGiver add constraint FK97D307DFD7D12F96 foreign key (id) references Interactor] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestParty_Avatar add constraint FK95530AD4405638B1 foreign key (questPartys_id) references QuestParty **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestParty_Avatar add constraint FK95530AD4405638B1 foreign key (questPartys_id) references QuestParty] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestParty_Avatar add constraint FK95530AD498005B7B foreign key (avatars_id) references Avatar **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestParty_Avatar add constraint FK95530AD498005B7B foreign key (avatars_id) references Avatar] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestParty_Quest add constraint FK5B23407405638B1 foreign key (questPartys_id) references QuestParty **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestParty_Quest add constraint FK5B23407405638B1 foreign key (questPartys_id) references QuestParty] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table QuestParty_Quest add constraint FK5B23407B51E1009 foreign key (quests_id) references Quest **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table QuestParty_Quest add constraint FK5B23407B51E1009 foreign key (quests_id) references Quest] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table Quest_ClueGiver add constraint FKD4BF26EB1012D8F5 foreign key (clueGivers_id) references ClueGiver **** 01-21@10:47:07 ERROR (SchemaExport.java:275) - Unexpected token: ALTER in statement [alter table Quest_ClueGiver add constraint FKD4BF26EB1012D8F5 foreign key (clueGivers_id) references ClueGiver] **** 01-21@10:47:07 ERROR (SchemaExport.java:274) - Unsuccessful: alter table Quest_ClueGiver add constraint FKD4BF26EBB51E1009 foreign key (quests_id) references Quest Best regards Farooq ahmad -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1258) startup time improvements

by Stefan Fleiter (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1258?page=c... ] Stefan Fleiter commented on HHH-1258: ------------------------------------- What's the state of this bug? The startup time is the major disadvantage of using hibernate (during development). This does not only cost money, but demotivates developers which is even more costly in the end. > startup time improvements > ------------------------- > > Key: HHH-1258 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1258 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Affects Versions: 3.1 rc3 > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Attachments: AbstractEntityTuplizer.patch, Environment.patch, LazyProxyFactory.patch, SessionFactoryImpl.java, SessionFactoryImpl.patch > > > while doing some basic startup perf testing the following were found - this issue is mainly to track what I find, and then fix it: > Initial tests where 100 classes, 30 sec for buildSessionFactory > setting hibernate.cglib.use_reflection_optimizer false and it is 10 sec for buildSessionFactory. > (maybe we should autodetect which jdk we are running on and disable it per default for 1.4/1.5 - needs to validate runtime impact) > Another (22%) time stealer is the discovery of getter/setters - in worst case it iterates over all declared methods per property. > (alternatively we could cache/sort this list or make a more efficient implementation if a class only contain default property accessors) > Other 20% of the time is done in net.sf.cglib related classes for build time enhancement. > The rest of the time is Configuration creation (can be cached) and other iteration code. > (p.s. don't take the % numbers as hard values - these are definitly affected by how many methods/classes you have; this underlying tests > is done on pojos with a "high" method count (approx 100) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-691) Allow @GeneratedValue-like feature on the TYPE level

by Paul Benedict (JIRA)

Allow @GeneratedValue-like feature on the TYPE level ---------------------------------------------------- Key: ANN-691 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-691 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.0.ga Reporter: Paul Benedict I have a generic hierarchy annotated as a @MappedSuperclass and a generic getId() method annotated as @Id. I use generics to specify the type, but I do not want to specify the generation strategy until the subclass. Since @GeneratedValue can only be applied to a FIELD or METHOD, there is no way to say it in Hibernate at the class level, which I think is a valuable extension. Since there can only be one ID per class, it makes sense allowing a look-a-like annotation at the TYPE level too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1036) XML Mapping support for generated Classes

by Walter Dorninger (JIRA)

XML Mapping support for generated Classes ----------------------------------------- Key: HBX-1036 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1036 Project: Hibernate Tools Issue Type: New Feature Components: reverse-engineer Affects Versions: 3.2.0.GA Environment: any Reporter: Walter Dorninger It would be a nice feature if it would be possible to include "XML Mapping" support when hbm files are reverse engineered. It seems that currently it is not possible to include the "node" tag in when tables are reverse engineered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Shyamsunder (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123?page=c... ] Shyamsunder commented on HHH-1123: ---------------------------------- I have faced the same issue in my project. After failed trails to find a suitable solution, I have written the method addRestrictions(). This method divides the List of values into sublists with size<=1000. It creates LogicalExpression using Restrictions.in() for each sublist. These LogicalExpressions are joined with OR condition using Restictions.or(); This methods returns Criterion object. private Criterion addRestrictions(String propertyName, List list) { int size = list.size(); int fromIndex = 0; int toIndex = (size>1000)?1000:size; List subList = list.subList(fromIndex, toIndex); Criterion lhs = Restrictions.in(propertyName, subList); toIndex = subList.size(); size = size-toIndex; while(size>0) { fromIndex=toIndex; toIndex += (size>1000)?1000:size; subList = list.subList(fromIndex, toIndex); Criterion rhs = Restrictions.in(propertyName, subList); lhs = Restrictions.or(lhs, rhs); size = size-subList.size(); }//while return lhs; } How to Use it: I have a class Employee with many to one reference to Person. Now I need to search for employees where person is IN list of person objects. So here is my HQL using the above method: List personsList; //Here personsList has more than 1000 entries. Criteria criteria = session.createCriteria(Employee.class).add(addRestrictions("person", personsList); List result = criteria.list(); P.S. I have executed this program with input size of 1050, 2100, 3100 and 3800 persons in personsList. I have recieved the following error message for all queries when personList.size>2000. So you have to increase shared memory on Oracle side. # of _persons: 2007 Jan 18, 2008 1:12:42 PM org.hibernate.util.JDBCExceptionReporter logExceptions WARNING: SQL Error: 4031, SQLState: 61000 Jan 18, 2008 1:12:42 PM org.hibernate.util.JDBCExceptionReporter logExceptions SEVERE: ORA-04031: unable to allocate 96 bytes of shared memory ("shared pool","select this_.id as id4_0_, t...","sql area","optdef : apanlg") > Cannot put more than 1000 elements in a InExpression > ---------------------------------------------------- > > Key: HHH-1123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc2, 3.2.0.alpha1 > Environment: Oracle 9i > Reporter: Alexis Seigneurin > Attachments: patch.txt > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The number of elements that we can put in a "in" expression is limited to a certain amount (1000 for Oracle, for instance). When creating a criteria query, the org.hibernate.criterion.InExpression class should split the expression into several smaller ones. > Attached is a patch which splits the expression by slices of 500 elements. For example, if we have 1001 elements to put in the "in" expression, the result would be : > (entity.field in (?, ?, ?...) or entity.field in (?, ?, ?...) or entity.field in (?)) > The surrounding parantheses are useful to avoid problems with other conditions (a "and" condition taking over the one of the "or" conditions). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-886) hbm2ddl generating too long index on MySQL

by James Carman (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-886?page=co... ] James Carman commented on HHH-886: ---------------------------------- Okay, so we have to go in and set up all the names manually. Seems a bit tedious, but I guess it's not too bad. Thank you for clarifying. I'm sure others will appreciate it when they Google and find this issue. > hbm2ddl generating too long index on MySQL > ------------------------------------------ > > Key: HHH-886 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-886 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: MySQL 4.1.11-standard, MyISAMI, table with default charset utf8 > Reporter: Oleg Marchuk > > SchemaExport log: > alter table CountryLocal drop foreign key FK610C39952D58FB2F; > drop table if exists CountryLocal; > drop table if exists schedule; > create table CountryLocal ( > id varchar(255) not null, > name varchar(255) not null, > lang varchar(255) not null, > primary key (id, lang) > ); > 17:19:59,997 ERROR SchemaExport:167 - Unsuccessful: create table CountryLocal (id varchar(255) not null, name varchar(255) not null, lang varchar(255) not null, primary key (id, lang)) > 17:20:00,003 ERROR SchemaExport:168 - Syntax error or access violation message from server: "Specified key was too long; max key length is 1000 bytes" > create table schedule ( > id varchar(255) not null, > primary key (id) > ); > alter table CountryLocal > add index FK610C39952D58FB2F (id), > add constraint FK610C39952D58FB2F > foreign key (id) > references schedule (id); > 17:20:00,014 ERROR SchemaExport:167 - Unsuccessful: alter table CountryLocal add index FK610C39952D58FB2F (id), add constraint FK610C39952D58FB2F foreign key (id) references schedule (id) > 17:20:00,015 ERROR SchemaExport:168 - Base table or view not found message from server: "Table 'test_oleg.CountryLocal' doesn't exist" > Mapping: > <?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="com.softzonenet"> > <class name="Test" table="schedule" lazy="false"> > <id name="id" type="string"> > <generator class="assigned" /> > </id> > <map name="names" lazy="false" table="CountryLocal" > cascade="delete"> > <key column="id" not-null="true" /> > <map-key type="string" column="lang" /> > <element type="string" column="name" not-null="true" /> > </map> > </class> > </hibernate-mapping> > Class: > package com.softzonenet; > public class Test { > > private String id = null; > > Test() { > > } > public String getId() { > return id; > } > public void setId(String id) { > this.id = id; > } > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-886) hbm2ddl generating too long index on MySQL

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-886?page=co... ] Max Rydahl Andersen commented on HHH-886: ----------------------------------------- index="blahblah" foreign-key="blablah" from the docs. > hbm2ddl generating too long index on MySQL > ------------------------------------------ > > Key: HHH-886 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-886 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: MySQL 4.1.11-standard, MyISAMI, table with default charset utf8 > Reporter: Oleg Marchuk > > SchemaExport log: > alter table CountryLocal drop foreign key FK610C39952D58FB2F; > drop table if exists CountryLocal; > drop table if exists schedule; > create table CountryLocal ( > id varchar(255) not null, > name varchar(255) not null, > lang varchar(255) not null, > primary key (id, lang) > ); > 17:19:59,997 ERROR SchemaExport:167 - Unsuccessful: create table CountryLocal (id varchar(255) not null, name varchar(255) not null, lang varchar(255) not null, primary key (id, lang)) > 17:20:00,003 ERROR SchemaExport:168 - Syntax error or access violation message from server: "Specified key was too long; max key length is 1000 bytes" > create table schedule ( > id varchar(255) not null, > primary key (id) > ); > alter table CountryLocal > add index FK610C39952D58FB2F (id), > add constraint FK610C39952D58FB2F > foreign key (id) > references schedule (id); > 17:20:00,014 ERROR SchemaExport:167 - Unsuccessful: alter table CountryLocal add index FK610C39952D58FB2F (id), add constraint FK610C39952D58FB2F foreign key (id) references schedule (id) > 17:20:00,015 ERROR SchemaExport:168 - Base table or view not found message from server: "Table 'test_oleg.CountryLocal' doesn't exist" > Mapping: > <?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="com.softzonenet"> > <class name="Test" table="schedule" lazy="false"> > <id name="id" type="string"> > <generator class="assigned" /> > </id> > <map name="names" lazy="false" table="CountryLocal" > cascade="delete"> > <key column="id" not-null="true" /> > <map-key type="string" column="lang" /> > <element type="string" column="name" not-null="true" /> > </map> > </class> > </hibernate-mapping> > Class: > package com.softzonenet; > public class Test { > > private String id = null; > > Test() { > > } > public String getId() { > return id; > } > public void setId(String id) { > this.id = id; > } > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1473) hbm2ddl validate seems to fail when views are involved

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1473?page=c... ] Max Rydahl Andersen commented on HHH-1473: ------------------------------------------ workaround: don't run with validation enabled. > hbm2ddl validate seems to fail when views are involved > ------------------------------------------------------ > > Key: HHH-1473 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1473 > Project: Hibernate3 > Issue Type: Bug > Components: metamodel > Affects Versions: 3.1 > Reporter: Emmanuel Bernard > Assignee: Diego Pires Plentz > Priority: Minor > > http://forum.hibernate.org/viewtopic.php?t=955341&start=0&postdays=0&post... > CategoryRanking is a view > org.hibernate.HibernateException: Missing table: CategoryRating > at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:953) > at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116) > at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:299) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1145) > at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:358) > at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:484) > at org.hibernate.ejb.Ejb3Configuration.createContainerEntityManagerFactory(Ejb3Configuration.java:202) > at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:78) > at org.jboss.ejb3.Ejb3Deployment.initializeManagedEntityManagerFactory(Ejb3Deployment.java:512) > at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:253) > at org.jboss.ejb3.Ejb3JmxDeployment.create(Ejb3JmxDeployment.java:230) > at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:34) > at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:245) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:228) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943) > at $Proxy0.create(Unknown Source) > at org.jboss.system.ServiceController.create(ServiceController.java:341) > at org.jboss.system.ServiceController.create(ServiceController.java:284) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) > at $Proxy10.create(Unknown Source) > at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:208) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) > at $Proxy11.create(Unknown Source) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753) > at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) > at $Proxy6.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:489) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:203) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:182) > 09:13:51,528 INFO [EJB3Deployer] Deployed: file:/C:/work/jboss-4.0.3SP1/server/default/deploy/bizmerit.ejb3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-886) hbm2ddl generating too long index on MySQL

by James Carman (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-886?page=co... ] James Carman commented on HHH-886: ---------------------------------- Would it be possible for someone to maybe add a URL where we can get more information on this? I am running into the same problem. Googling comes up with this issue as the first place to find information, so it could be useful to other folks in the future. > hbm2ddl generating too long index on MySQL > ------------------------------------------ > > Key: HHH-886 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-886 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: MySQL 4.1.11-standard, MyISAMI, table with default charset utf8 > Reporter: Oleg Marchuk > > SchemaExport log: > alter table CountryLocal drop foreign key FK610C39952D58FB2F; > drop table if exists CountryLocal; > drop table if exists schedule; > create table CountryLocal ( > id varchar(255) not null, > name varchar(255) not null, > lang varchar(255) not null, > primary key (id, lang) > ); > 17:19:59,997 ERROR SchemaExport:167 - Unsuccessful: create table CountryLocal (id varchar(255) not null, name varchar(255) not null, lang varchar(255) not null, primary key (id, lang)) > 17:20:00,003 ERROR SchemaExport:168 - Syntax error or access violation message from server: "Specified key was too long; max key length is 1000 bytes" > create table schedule ( > id varchar(255) not null, > primary key (id) > ); > alter table CountryLocal > add index FK610C39952D58FB2F (id), > add constraint FK610C39952D58FB2F > foreign key (id) > references schedule (id); > 17:20:00,014 ERROR SchemaExport:167 - Unsuccessful: alter table CountryLocal add index FK610C39952D58FB2F (id), add constraint FK610C39952D58FB2F foreign key (id) references schedule (id) > 17:20:00,015 ERROR SchemaExport:168 - Base table or view not found message from server: "Table 'test_oleg.CountryLocal' doesn't exist" > Mapping: > <?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="com.softzonenet"> > <class name="Test" table="schedule" lazy="false"> > <id name="id" type="string"> > <generator class="assigned" /> > </id> > <map name="names" lazy="false" table="CountryLocal" > cascade="delete"> > <key column="id" not-null="true" /> > <map-key type="string" column="lang" /> > <element type="string" column="name" not-null="true" /> > </map> > </class> > </hibernate-mapping> > Class: > package com.softzonenet; > public class Test { > > private String id = null; > > Test() { > > } > public String getId() { > return id; > } > public void setId(String id) { > this.id = id; > } > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1473) hbm2ddl validate seems to fail when views are involved

by Eric Smith (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1473?page=c... ] Eric Smith commented on HHH-1473: --------------------------------- I am hitting this issue using MSSQL and wondering if someone can begin working on a fix? I am using JBoss 4.2.2.GA which appears to use hibernate-entitymanager.jar version of 3.2.1.GA. In this example mbi_user_v is a view. Changing it to a table results in deploying properly. 10:22:59,215 WARN [ServiceController] Problem starting service persistence.units:ear=hbi.ear,jar=hbi.jar,unitName=HBIMain javax.persistence.PersistenceException: org.hibernate.HibernateException: Missing table: mbi_user_v at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:720) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor362.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy386.start(Unknown Source) at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120) at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:627) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:351) at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor362.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy33.start(Unknown Source) at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy34.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.hibernate.HibernateException: Missing table: mbi_user_v at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1080) at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:317) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:713) ... 99 more > hbm2ddl validate seems to fail when views are involved > ------------------------------------------------------ > > Key: HHH-1473 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1473 > Project: Hibernate3 > Issue Type: Bug > Components: metamodel > Affects Versions: 3.1 > Reporter: Emmanuel Bernard > Assignee: Diego Pires Plentz > Priority: Minor > > http://forum.hibernate.org/viewtopic.php?t=955341&start=0&postdays=0&post... > CategoryRanking is a view > org.hibernate.HibernateException: Missing table: CategoryRating > at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:953) > at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:116) > at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:299) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1145) > at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:358) > at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:484) > at org.hibernate.ejb.Ejb3Configuration.createContainerEntityManagerFactory(Ejb3Configuration.java:202) > at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:78) > at org.jboss.ejb3.Ejb3Deployment.initializeManagedEntityManagerFactory(Ejb3Deployment.java:512) > at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:253) > at org.jboss.ejb3.Ejb3JmxDeployment.create(Ejb3JmxDeployment.java:230) > at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:34) > at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:245) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:228) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943) > at $Proxy0.create(Unknown Source) > at org.jboss.system.ServiceController.create(ServiceController.java:341) > at org.jboss.system.ServiceController.create(ServiceController.java:284) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) > at $Proxy10.create(Unknown Source) > at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:208) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) > at $Proxy11.create(Unknown Source) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753) > at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) > at $Proxy6.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:489) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:203) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:182) > 09:13:51,528 INFO [EJB3Deployer] Deployed: file:/C:/work/jboss-4.0.3SP1/server/default/deploy/bizmerit.ejb3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1785) validate not working with oracle dblinks

by Ben Turner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1785?page=c... ] Ben Turner commented on HHH-1785: --------------------------------- I use Oracle database links with Public Synonyms, and have a related problem. My table, lets call it DATA@OTHERDB is owned by DB_OWNER. So we have setup a view to the table called DATA_V, again owned by DB_OWNER, that points at the table. Then finally we have a public synonym pointing DATA at DB_OWNER.DATA_V However, I get trouble when using Chris Richardson's ORMUnit ( http://ormunit.googlecode.com) which sets up a Hibernate Configuration object then calls configuration.generateSchemaUpdateScript(dialect, dbmd) which it then would go on to parse the output for missing / extra items. This call fails with the following in the logs: 2008-01-18 12:00:13,714 [main] INFO org.hibernate.tool.hbm2ddl.TableMetadata - table found: DB_OWNER.LOCAL_TABLE 2008-01-18 12:00:13,714 [main] INFO org.hibernate.tool.hbm2ddl.TableMetadata - columns: [id, column1, other_column] 2008-01-18 12:00:13,714 [main] INFO org.hibernate.tool.hbm2ddl.TableMetadata - foreign keys: [...] 2008-01-18 12:00:13,714 [main] INFO org.hibernate.tool.hbm2ddl.TableMetadata - indexes: [...] 2008-01-18 12:00:13,729 [main] INFO org.hibernate.tool.hbm2ddl.DatabaseMetadata - table not found: DATA So I am guessing the schema update script is presuming the table is local and not over a database link. > validate not working with oracle dblinks > ---------------------------------------- > > Key: HHH-1785 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1785 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.1 rc2 > Environment: Hibernate: 3.1.rc2 > Database: Oracle 9i > Reporter: Arik Galansky > > Full stack trace of any exception that occurs: > Don't have a full stack availible, but here is the last part: > Caused by:org.hibernate.HibernateException: Missing Table: table@dblink > org.hibernate.cfg.Configuration.ValidateSchema (Configuration.java953) > Name and version of the database you are using: Oracle 9i > the problem is that when I set the hibernate.hbm2ddl.auto to validate I get the mentioned below Exception on a table that is found on a remote DB/ > important to note that I can select from the table when it comes to queries, but only if I put it the hbm2ddl on "update" mode which is ofcourse not healthy considering I don't want the EJB to alternate my DB stracture in any way. > * important to mention that the user on the other side of the DBlink has the "select any dictionary" grant so he should have no problem selecting from the dba_* tables. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-582) Joda User Types

by Martin Gilday (JIRA)

Joda User Types --------------- Key: ANN-582 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-582 Project: Hibernate Annotations Type: New Feature Versions: 3.2.1 Reporter: Martin Gilday Attachments: jodaUserTypes.zip As discussed on the forums http://forum.hibernate.org/viewtopic.php?t=972083 here are some user types for Joda Time. It covers LocalDate, LocalDateTime and LocalTime checked against Joda 1.4. Currently it has been used with MySql4.x. It relies on using date patterns for converting the joda objects and then setting them as Strings. This should work for any database that uses the same date/time formats. One possible improvement might be to convert to java.sql.Date etc and allow JDBC to handle the setting in the DB. Although I do not know how this would affect timezones, which was the reason for using LocalXxx. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

3
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1476) Table.qualify does not handle dialect diferences

by Krashan Brahmanjara (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1476?page=c... ] Krashan Brahmanjara commented on HHH-1476: ------------------------------------------ Last post got mistake I only suggest do not rename method table.qualify to table.internalIdentifier. > Table.qualify does not handle dialect diferences > ------------------------------------------------ > > Key: HHH-1476 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1476 > Project: Hibernate3 > Issue Type: Bug > Components: core > Environment: Hibernate 3.1.2 > SQL Server 2000 > Reporter: Justin Kolb > Attachments: informix-table-qname-patch-NPAC-vs-v324sp1.diff, informix-table-qname-patch-NPAC.diff, informix-table-qname-patch.diff > > > The fix for HHH-699 caused me to discover that Hibernate isn't handling qualifying table names properly. It can be inferred from HHH-699 that not all databases are similar in this respect so I think this should be added to the dialect handling. From my short research I have the following 3 cases: > SQL Server: database.owner.table > MySQL: database.table (no schemas it seems) > Most others: catalog.schema.table > SQL Server also allows for "database..table" since it does not have schemas but does allow you to write queries that cross databases similar to how you can cross schemas in other database servers. > Testing on Postgres though I determined that it does not allow "catalog..table" and will only accept "catalog.schema.table", so it dos not match up with SQL Server in this respect. If you write "catalog.table" it thinks you are trying to use a schema so it does not match up with MySQL in this respect. > So right now only MySQL and SQL Server are the non standard compliant databases. Before 3.1 beta 1, SQL Server was handled correctly; then after that only MySQL was handled correctly. > I'm not sure how much work it would take to make this change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-50) @Valid does not properly validate collections

by Kevin Conaway (JIRA)

@Valid does not properly validate collections --------------------------------------------- Key: HV-50 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-50 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 3.0.0.ga Reporter: Kevin Conaway Attachments: validator.patch The @Valid annotation does not properly validate collections. Attached is a patch with a failing test case: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1523) LazyInitializationError on enabling query cache...

by Travis Camechis (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1523?page=c... ] Travis Camechis commented on HHH-1523: -------------------------------------- I too have been experiencing this issue when enabling query cache. The workaround does work but is very much a pain with a large object graph and inheritance involved. > LazyInitializationError on enabling query cache... > -------------------------------------------------- > > Key: HHH-1523 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1523 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5, 3.1 > Environment: 3.0.1 and 3.1, HSQLDB and Oracle > Reporter: Vikas Sasidharan > Attachments: cache_issue.log, QueryCacheIssue.zip > > > I have two domain objects - Employee and Department - and there is a 1:N relationship from Department to Employee. When I join fetch an Employee with its Department, without query cache enabled, it works fine. If I enable query cache for this same query, it bombs with a LazyInitializationException. > Notes: > 1) We get this error only if query cache is enabled. > 2) We observed the same behaviour on both oscache and ehcache > 3) Calling Hibernate.initialize() explicitly after firing the HQL seems to work. The initialization does not fire an extra query though (it seems to pick it from the cache). > 4) Setting "lazy=false" on the "many-to-one" mapping also works. However, it wouldn't be acceptable. > Hibernate version: 3.0.5 > Mapping documents: > Employee.hbm.xml > <hibernate-mapping> > <class name="tavant.platform.test.domain.Employee" > table="CACHE_ISSUE_EMP" lazy="true" dynamic-update="true" dynamic-insert="true"> > <cache usage="read-write" /> > <id name="id" column="EMP_ID" type="java.lang.Long" > access="field" unsaved-value="null"> > <generator class="increment" /> > </id> > > <property name="name" type="string" update="true" > insert="true" column="EMP_NAME"/> > <many-to-one name="department" class="tavant.platform.test.domain.Department" > cascade="none" outer-join="auto" update="true" insert="true" column="DEPARTMENT_ID"/> > </class> > </hibernate-mapping> > > Department.hbm.xml > <hibernate-mapping> > <class name="tavant.platform.test.domain.Department" table="CACHE_ISSUE_DEP" > lazy="true" dynamic-update="true" dynamic-insert="true"> > > <cache usage="read-write" /> > <id name="id" column="DEPARTMENT_ID" > type="java.lang.Long" access="field"> > <generator class="increment"/> > </id> > <property name="name" type="java.lang.String" > update="false" insert="true" column="NAME"/> > <bag name="employees" lazy="true" > inverse="true" cascade="save-update" access="field"> > <cache usage="read-write"/> > <key column="DEPARTMENT_ID"/> > <one-to-many class="tavant.platform.test.domain.Employee"/> > </bag> > </class> > </hibernate-mapping> > > Code between sessionFactory.openSession() and session.close(): > public Employee getEmployeeWithDepartment(String empName) { > Session session = null; > try { > session = sessionFactory.openSession(); > Employee emp = (Employee) session.createQuery( > "from Employee e join fetch e.department where e.name = :name") > .setString("name", empName) > .setCacheable(true) > .uniqueResult(); > // If I uncomment the next line, this works (even without > // firing an extra query)! > // Hibernate.initialize(emp.getDepartment()); > return emp; > } finally { > if (session != null) { > session.close(); > } > } > } > > // First load employee and populate cahces > Employee emp = test.getEmployeeWithDepartment(EMPLOYEE_NAME); > System.out.println("Employee : " + emp + ", Employee.Department : " > + emp.getDepartment()); > > // Now try to make use of the cache > emp = test.getEmployeeWithDepartment(EMPLOYEE_NAME); > System.out.println("Employee : " + emp + ", Employee.Department : " > + emp.getDepartment()); > > Full stack trace of any exception that occurs: > org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed > at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:53) > at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:84) > at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:134) > at tavant.platform.test.domain.Department$$EnhancerByCGLIB$$67b26899.toString(<generated>) > at java.lang.String.valueOf(String.java:2131) > at java.lang.StringBuffer.append(StringBuffer.java:370) > at tavant.platform.test.client.TestPrefetchRelationWithQueryCacheEnabled.main(TestPrefetchRelationWithQueryCacheEnabled.java:116) > > Name and version of the database you are using: > We have noticed this on Oracle and HSQL > The generated SQL (show_sql=true): > #First read, goes fine > Hibernate: select employee0_.EMP_ID as EMP1_0_, department1_.DEPARTMENT_ID as DEPARTMENT1_1_, employee0_.EMP_NAME as EMP2_1_0_, employee0_.DEPARTMENT_ID as DEPARTMENT3_1_0_, department1_.NAME as NAME0_1_ from CACHE_ISSUE_EMP employee0_ inner join CACHE_ISSUE_DEP department1_ on employee0_.DEPARTMENT_ID=department1_.DEPARTMENT_ID where (employee0_.EMP_NAME=? ) > #Prints the Employee and Department fine > Employee : [Id : 1, name : testEmployee], Employee.Department : [Id : 1, name : testDepartment] > #Second read bombs! > org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed > at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:53) > at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:84) > at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:134) > [..] > Please have a look at the post [http://forum.hibernate.org/viewtopic.php?t=955839] for more details and follow ups. > Kindly help. I am attaching an Eclipse Project containing the TestCase. The main file is TestPrefetchRelationWithQueryCacheEnabled. > Thanks, > Vikas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3070) Pagination support for criteria queries

by marko asplund (JIRA)

Pagination support for criteria queries ---------------------------------------- Key: HHH-3070 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3070 Project: Hibernate3 Issue Type: Improvement Reporter: marko asplund It would good if it would be possible to use the criteria query api for specifying the result set window e.g. so that Criteria c = session.createCriteria(Cat.class); c.setResultSetWindow(500000, 20); would make the database return the first 20 rows starting from row 500000 of the total result set. Currently it's possible to do this in the application level but a lot of work would be saved when the database would not need to return 500000 rows which are then OR mapped only to be discarded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3073) Make getParameter(String) available via the Filter interface

by David Hudson (JIRA)

Make getParameter(String) available via the Filter interface ------------------------------------------------------------ Key: HHH-3073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3073 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Environment: All Reporter: David Hudson Priority: Minor Currently the Filter interface does not expose the getParameter(String) method that is available on the FilterImpl implementation. This would be usefull to allow filter parameters to be accessed and saved at runtime thus allowing a filter to be temporarily disabled and reenabled (followed by the reapplication of the paramters). The current action when disabling and then re-enabling a filter causes the Filter to be recreated and the parameters lost. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-657) improve foreign key constraint name docs and inverse generation

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-657?page=co... ] Max Rydahl Andersen commented on HBX-657: ----------------------------------------- robert - I don't understand what that fix has to do with this issue...are you sure you are not talking about some other issue ? Please open another issue for that with info on what your patch actually fixes ? thanks > improve foreign key constraint name docs and inverse generation > --------------------------------------------------------------- > > Key: HBX-657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-657 > Project: Hibernate Tools > Issue Type: Improvement > Affects Versions: 3.1.beta5 > Reporter: Max Rydahl Andersen > Fix For: 3.2.1 > > > <foreign-key constraint-name/> > > Documentation for the constraint-name attribute has to be improved. What exactly is this? Is it something that comes from the database (I know it is)? The > foreign key constraint name is not generated/included in the <many-to-one> column or the collection key column in the hbm.xml file. The set is > inverse="true", even if <many-to-one> is excluded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-657) improve foreign key constraint name docs and inverse generation

by Robert van Eersel (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-657?page=co... ] Robert van Eersel commented on HBX-657: --------------------------------------- Proposed change to CfgHbmTool.java: public String getForeignKeyName(Property property) { if (isManyToOne(property)) { Value value = property.getValue(); Iterator i = value.getTable().getForeignKeyIterator(); ForeignKey foreignKey = (ForeignKey) i.next(); if(i.hasNext()) { log.warn("More than one foreign key found for property: " + property.getName()); } if (foreignKey != null) { return foreignKey.getName(); } } return ""; } Proposed change to many-to-one.hbm.ftl: <#assign foreignkey = c2h.getForeignKeyName(property)> <#if foreignkey != ""> foreign-key="${foreignkey}" </#if> > improve foreign key constraint name docs and inverse generation > --------------------------------------------------------------- > > Key: HBX-657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-657 > Project: Hibernate Tools > Issue Type: Improvement > Affects Versions: 3.1.beta5 > Reporter: Max Rydahl Andersen > Fix For: 3.2.1 > > > <foreign-key constraint-name/> > > Documentation for the constraint-name attribute has to be improved. What exactly is this? Is it something that comes from the database (I know it is)? The > foreign key constraint name is not generated/included in the <many-to-one> column or the collection key column in the hbm.xml file. The set is > inverse="true", even if <many-to-one> is excluded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3072) Comments in HQL

by Fol De Rol (JIRA)

Comments in HQL --------------- Key: HHH-3072 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3072 Project: Hibernate3 Issue Type: Improvement Components: query-hql Reporter: Fol De Rol As far as I understood from grammar fiiles, there is no such a concept as commentaries in HQL. Seems rather strange. Sometimes it's needed to make short notes within HQL queries. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3069) ObjectNotFoundException when proxy exists for super class of non existant joined subclass

by dan oxlade (JIRA)

ObjectNotFoundException when proxy exists for super class of non existant joined subclass ----------------------------------------------------------------------------------------- Key: HHH-3069 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3069 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Reporter: dan oxlade A proxy of an entity which has a joined subclass is loaded into the session. If the proxy resolves to null, i.e the id of the proxy has no matching row in the database then future queries (in the same hibernate session) for any of the joined subclass entities will fail with ObjectNotFoundExceptions from the returnNarrowedProxy method of the DefaultLoadEventListener. the following test method in JoinedSubclassTest demonstrates the failing test: public void testProxyLoadedWhichDoesNotExist() throws Exception { Session s = openSession(); Transaction t = s.beginTransaction(); Long id = Long.valueOf(0L); Employee employee = (Employee) s.get(Employee.class,id); assertNull(employee); Person proxy = (Person) s.load(Person.class,id); assertNotNull(proxy); employee = (Employee) s.get(Employee.class,id); assertNull(employee); t.commit(); s.close(); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3067) Request to rename TimesTenDialect class to TimesTen5Dialect

by Jason Feldhaus (JIRA)

Request to rename TimesTenDialect class to TimesTen5Dialect ----------------------------------------------------------- Key: HHH-3067 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3067 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5.ga, TimesTen 5.1.x Reporter: Jason Feldhaus Priority: Minor Two new TimesTen dialect classes have been submitted for inclusion into the Hibernate distribution: 1. TimesTen7Dialect (see HHH-3061) 2. TimesTen6Dialect (see HHH-3066) In order to unambiguously identify the TimesTen version associated with the existing org.hibernate.dialect.TimesTenDialect class that is currently included in the Hibernate distribution we request that this existing class be renamed to the following: org.hibernate.dialect.TimesTen5Dialect We have discussed this change with Steve Ebersole. Please direct any questions to Jason Feldhaus (jason.feldhaus(a)oracle.com). Thank you, Jason -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3066) New TimesTen6Dialect class for Oracle TimesTen In-Memory Database v 6.x

by Jason Feldhaus (JIRA)

New TimesTen6Dialect class for Oracle TimesTen In-Memory Database v 6.x ----------------------------------------------------------------------- Key: HHH-3066 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3066 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5.ga, TimesTen 6.0.9 Reporter: Jason Feldhaus Priority: Minor Attachments: TimesTen6Dialect.zip A new TimesTen dialect class has been developed for TimesTen version 6.x releases. This dialect reflects all of the SQL improvements made to the TimesTen 6 product since the original TimesTenDialect class was developed for Hibernate several years ago. After consulting with Steve Ebersole, our ultimate goal is to have this new TimesTen6Dialect class be included in the official Hibernate distribution. Also see issue HHH-3061 for a new dialect class for TimesTen version 7.x. The attached zip file contains the following: 1. TimesTen6Dialect.java (A new dialect class for use with TimesTen version 6.x releases) 2. TimesTen6Dialect ChangeLog.txt (A list of changes in relation to the original TimesTenDialect currently included in the Hibernate distribution) 3. Hibernate TimesTen6Dialect Test Results.xls (A spreadsheet describing the reasons for test case failures when running this new dialect class with the Hibernate test suite.) Please direct any questions to Jason Feldhaus (jason.feldhaus(a)oracle.com). Thank you, Jason -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1673) hql parsed with exception (with clause)

by Jon Hoffman (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1673?page=c... ] Jon Hoffman commented on HHH-1673: ---------------------------------- I am hitting the same issue with 3.2. I voted to have this fixed because it prevents a lot of complex queries when native SQL is not an option. I have had to "upgrade" to using 3.1.2 version of Hibernate so my queries will run without throwing an exception. > hql parsed with exception (with clause) > --------------------------------------- > > Key: HHH-1673 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1673 > Project: Hibernate3 > Issue Type: Deprecation > Components: query-hql > Affects Versions: 3.1.3 > Reporter: Tomasz Bech > Attachments: HHH-1673.patch, HHH-1673.patch > > > The 'improvement' bug fix: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1520 > has broken working functionality: > I found that after switching to 3.1.3 following construction is not working any longer: > (FootnoteTypeBO has collection 'descriptions' and reference to languageBO) > from FootnoteTypeBO as o > left outer join o.descriptions as t1 > with (t1.language in (select loid from LanguageBO where name = 'aa')) > --> exception: 'with-clause referenced two different from-clause elements'. > There is no implicit join as dewscribed in main anomaly, so it shouldn't cause the problem. So now there is no way to write correct hql/sql, and I don't see any workaround. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-149) Default FieldBridge for enums passing wrong class to EnumBridge constructor

by Marcio Silva (JIRA)

Default FieldBridge for enums passing wrong class to EnumBridge constructor --------------------------------------------------------------------------- Key: HSEARCH-149 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-149 Project: Hibernate Search Issue Type: Bug Components: mapping Affects Versions: 3.0.0.GA Reporter: Marcio Silva Default FieldBridge for enums introduced in HSEARCH-2 added the following block to BridgeFactory: 119 + if ( bridge == null && returnType.isEnum() ) { 120 + bridge = new TwoWayString2FieldBridgeAdaptor( 121 + new EnumBridge( (Class<? extends Enum>) returnType.getClass() ) 122 + ); 123 + } This results in errors unmarshalling as the class passed to the EnumBridge constructor will be the XClass implementation class for the returnType variable. The code probably needs to load the class by name from returnType, or cast returnType to a JavaXClass to utilize the toClass() method instead of getClass() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3065) i am trying to add two fields in the my sql database and i am coming across these errors like no suitable errors and also could not find complete schema update

by isaacpradeep (JIRA)

i am trying to add two fields in the my sql database and i am coming across these errors like no suitable errors and also could not find complete schema update --------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3065 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3065 Project: Hibernate3 Issue Type: Task Environment: windows ;jdk1.4;eclipse3.2;mysql; Reporter: isaacpradeep Attachments: student.rar Name: isaac Degree: be Phone: 1234 31 [main] WARN org.hibernate.cfg.SettingsFactory - Could not obtain connection metadata java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:68) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1509) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1054) at student.AddStudent.main(AddStudent.java:28) 719 [main] WARN net.sf.ehcache.config.Configurator - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/E:/hibernate/workspace/hibernate/lib/ehcache-1.1.jar!/ehcache-failsafe.xml 2031 [main] ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - could not get database metadata java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110) at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:118) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:263) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1055) at student.AddStudent.main(AddStudent.java:28) 2031 [main] ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - could not complete schema update java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110) at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:118) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:263) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1055) at student.AddStudent.main(AddStudent.java:28) 2875 [main] WARN org.hibernate.util.JDBCExceptionReporter - SQL Error: 0, SQLState: 08001 2875 [main] ERROR org.hibernate.util.JDBCExceptionReporter - No suitable driver org.hibernate.exception.GenericJDBCException: Cannot open connection at org.hibernate.exception.ErrorCodeConverter.handledNonSpecificException(ErrorCodeConverter.java:92) at org.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:80) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) at org.hibernate.jdbc.AbstractBatcher.openConnection(AbstractBatcher.java:427) at org.hibernate.jdbc.JDBCContext.connect(JDBCContext.java:168) at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:103) at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:49) at org.hibernate.transaction.JDBCTransactionFactory.beginTransaction(JDBCTransactionFactory.java:24) at org.hibernate.jdbc.JDBCContext.beginTransaction(JDBCContext.java:231) at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1073) at student.AddStudent.main(AddStudent.java:35) Caused by: java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110) at org.hibernate.jdbc.AbstractBatcher.openConnection(AbstractBatcher.java:424) ... 7 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-124) Double lucene document created when inserting entities (@IndexEmbedded)

by Amin Mohammed-Coleman (JIRA)

Double lucene document created when inserting entities (@IndexEmbedded) ----------------------------------------------------------------------- Key: HSEARCH-124 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-124 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.0.cr1 Environment: Hibernate version: 3.2.5.ga Database platform: MySQL OS: Mac OS 10.4.10 Spring Framework 2.0 Reporter: Amin Mohammed-Coleman Attachments: phone-app.zip When inserting an entity using hibernate, double lucene documents are created for entities associated with the original entity. Please refer to : http://forum.hibernate.org/viewtopic.php?t=980102 For example the below code used to populate/create a Contact entity produces two lucene documents for Address and Phone entities. The database has only entry for the Address and Phone. [code] Address address = new Address(); address.setAddress1("TEST1"); address.setAddress2("N/A"); address.setTown("TEST TOWN"); address.setCounty("TEST COUNTY"); address.setCountry("UK"); address.setPostcode("XXXXXXX"); address.setActive(true); address.setCreatedOn(new Date()); address.setLastUpdatedOn(new Date()); Phone phone = new Phone(); phone.setNumber("01273234122"); phone.setType("HOME"); phone.setCreatedOn(new Date()); phone.setLastUpdatedOn(new Date()); PersonalContact contact = new PersonalContact(); contact.setFirstname("Amin"); contact.setSurname("Mohammed-Coleman"); contact.setEmail("address(a)hotmail.com"); contact.setDateOfBirth(new Date()); contact.setNotifyBirthDay(false); contact.setCreatedOn(new Date()); contact.setLastUpdatedOn(new Date()); contact.setNotes("TEST"); contact.addAddressToContact(address); contact.addPhoneToContact(phone); ApplicationContext appCtx = new ClassPathXmlApplicationContext(new String[]{"/spring/context-dao.xml"}); ContactDao contactDao = (ContactDao)appCtx.getBean("contactDao"); contactDao.createContact(contact); List<Contact> contacts = contactDao.search("address(a)hotmail.com"); System.out.println("contacts = " + contacts); [/code] Please find attached the entities I am using. I am not sure if there is enough information but the post provides all the information. Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-148) Hibernate Search does not integrate well with the Spring Framework - FullTextSessionImpl needs fixes

by Michael Lossos (JIRA)

Hibernate Search does not integrate well with the Spring Framework - FullTextSessionImpl needs fixes ---------------------------------------------------------------------------------------------------- Key: HSEARCH-148 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-148 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.0.GA Reporter: Michael Lossos We are integrating Hibernate Search (3.0.0 GA) into an existing Hibernate / Spring Framework / Eclipse RCP configuration. Unfortunately, Hibernate Search's FullTextSessionImpl assumes that it will be passed an org.hibernate.classic.Session. When using Spring for Hibernate transaction management, Spring creates a defensive Proxy that disables the Session.close() method. This Proxy does not implement the EventSource nor classic.Session, while Hibernate Search assumes that it does and has a ClassCastException in the FullTextSessionImpl constructor. Hibernate Search's FullTextSessionImpl does this which is wrong for the Spring Hibernate Session Proxy: public FullTextSessionImpl(org.hibernate.Session session) { this.session = (Session) session; // classic.Session! this.eventSource = (EventSource) session; this.sessionImplementor = (SessionImplementor) session; } It should be possible to rewrite FullTextSession and FullTextSessionImpl so that they do not use the org.hibernate.classic.Session but instead use the standard Hibernate Session, and thus avoid the unsafe casting. The workaround for this is to use HibernateTemplate.setExposeNativeSession( true ) before executing the HibernateCallback (causing the SessionImpl to be passed directly, without a Proxy). This exposes the Session to potential close() and is *not* a good idea. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Resolved: (EJB-152) Check JBossEJB3 entityexception tests for missing Exceptions

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-152?page=co... ] Emmanuel Bernard resolved EJB-152. ---------------------------------- Resolution: Fixed Done a long time ago > Check JBossEJB3 entityexception tests for missing Exceptions > ------------------------------------------------------------ > > Key: EJB-152 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-152 > Project: Hibernate Entity Manager > Issue Type: Bug > Components: EntityManager > Affects Versions: 3.1beta7 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-285) EJB3 compliant default settings override hibernate.cfg.xml

by Rodolfo Federico Gamarra (JIRA)

EJB3 compliant default settings override hibernate.cfg.xml ---------------------------------------------------------- Key: EJB-285 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-285 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: Hibernate 3.2.1 Hibernate EntityManager 3.3.1.GA Reporter: Rodolfo Federico Gamarra Priority: Minor Attachments: entitymanager-configuration.zip Hi, I think I've found a little bug in org.hibernate.ejb.Ejb3Configuration ($Id: Ejb3Configuration.java 11344 2007-03-25 18:24:01Z epbernard $) class. Hopefully the title is clear enough to describe what's happening: - I've a persitence.xml which references (via "hibernate.ejb.cfgfile") a hibernate.cfg.xml, in the way that's described, for example, in the Entity Manager User Guide (Version: 3.3.1.GA. Page 8, below "Here is a typical configuration in a J2SE environment"). - In the referenced xml I set the auto commmit property in false and in persistence.xml nothing it's said about that property. - What I see at the end of the startup is that the value is true. Posible explanation: - Take a look at Ejb3Configuration, specially the methods: - configure(Properties properties, Map workingVars) - prepareProperties(Properties properties, Map workingVars) - A pseudo-code for the first may be: 1) Prepare properties (load persistence.xml): //settings that always apply to a compliant EJB3 preparedProperties.setProperty( Environment.AUTOCOMMIT, "true" ); 2) Load the referenced "hibernate.ejb.cfgfile". I saw in debugging that the actual false value gets loaded. 3) Priorize persistence.xml over hibernate.cfg.xml: cfg.addProperties( preparedProperties ); //persistence.xml has priority over hibernate.Cfg.xml The problem with the last line (besides the typo in the comment, in the extension :-)) is that, I think, that priorization doesn't consider that maybe the values in the prepared properties are there because a default (and not because they were acctually configured in the xml). After reading "READ THIS BEFORE USING JIRA!", I took a look in the already reported things but didn't get to the problem (In fact, I was using an older verion and, so, I made an update and tried with the lattest one). Also, as you say "Don't attach your project folder as a Zip file, but only the relevant files. Please don't upload them one-by-one, but packaged in a Zip": I made a dummy project (Eclipse 3.2) which shows the problem. I setup log4j properties into debug mode, where the beforementioned can be saw. Also I added some reflection code in order to see the configuration values after the startup process has finished. I also used some other properties in order to have some combinations: a property defined in both xmls (persistence wins), just in persistence, just in hibernate and gets overrided (autocommit), just in hibernate but doesn't get overrided (user name). I hope that I didn't misundertood "...don't attach your project...", what I attached is a tiny-example-oriented project; from which the relevant files are "persistence.xml" and "hibernate.cfg.xml". In the heading of the log (which is in root of the project in console.txt) you can see the versions of Hibernate, in particular Hibernate EntityManager 3.3.1.GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-291) Cascade delete not working when set in the ORM.file

by breako (JIRA)

Cascade delete not working when set in the ORM.file --------------------------------------------------- Key: EJB-291 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-291 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.2.0.cr2 Environment: Annotations: Version: 3.2.0 CR1 Core: version 3.2 cr2 EntityManager: Version: 3.2.0.CR1 Oracle 10. Reporter: breako Attachments: hibernatetests.zip Hi, I posted this problem in the forums and was advised to created a JIRA. http://forum.hibernate.org/viewtopic.php?p=2353362#2353362 Basically, when Cascade-Persist is set in the ORN.xml file it does not work. I have attached a zip to show the simpliest possible case when this does not work. All source files etc. included. Please see the readme.txt for more info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2677) Not loading the ORM.xml file

by Adi (JIRA)

Not loading the ORM.xml file ---------------------------- Key: HHH-2677 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2677 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.0.ga Environment: Windows XP,MySQL5.0,Hibernate3.2.0 Reporter: Adi Priority: Minor Attachments: persistence.zip IF the name of the orm.xml is anything different, then Hibernate is not loading the orm file. Following is the error I am getting: java.lang.ExceptionInInitializerError at com.iChieve.domain.entity.ProductCategoryUnitTest.testSave(ProductCategoryUnitTest.java:16) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: javax.persistence.PersistenceException: [PersistenceUnit: simpleJPA-PersistenceUnit] Unable to find XML mapping file in classpath: /META-INF/myorm.xml at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:914) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:772) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:183) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:240) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:120) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:51) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:33) at com.iChieve.dao.EntityManagerHelper.<clinit>(EntityManagerHelper.java:20) ... 17 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (EJB-299) JarVisitor.addElement() fails with a StringIndexOutOfBoundsException if there is a package-info.class in the default package.

by Heiko Burchard (JIRA)

JarVisitor.addElement() fails with a StringIndexOutOfBoundsException if there is a package-info.class in the default package. ----------------------------------------------------------------------------------------------------------------------------- Key: EJB-299 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-299 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Windows XP, Eclipse 3.2.2, JDK 1.5.0_11 and 1.6.0_01 Reporter: Heiko Burchard Line 252: String name = entryName.substring( 0, entryName.length() - ".package-info.class".length() ).replace( '/', '.' ); tries to substring the String "package-info.class" from 0 to ".package-info.class" - this can not work... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Resolved: (EJB-192) Serialization exception with hashCode() and eager-eager

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-192?page=co... ] Emmanuel Bernard resolved EJB-192. ---------------------------------- Resolution: Rejected Done contemplating > Serialization exception with hashCode() and eager-eager > ------------------------------------------------------- > > Key: EJB-192 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-192 > Project: Hibernate Entity Manager > Issue Type: Bug > Components: EntityManager > Affects Versions: 3.2.0.cr1 > Environment: JBoss 4.0.4.GA-patch1 and SUN JDK 1.5.0_07 on Windows XP > Reporter: Stefan Norberg > Attachments: eager-eager.jar > > > I have a problem with some weird stuff going on when I implement the equals()/hashCode() methods in my entites. The short version is that I get a NullPointerException on deserialization on the client side after a remote server request when I am using eager fetching in both Team and Player. If I set the player-> team to lazy it works. > More details are on the Hibernate forum: > http://forum.hibernate.org/viewtopic.php?p=2308640#2308640 > I'm going to post the test case here tomorrow when I get the code from work. > All the fields in the entity are null when the the object hits the deserialization code and hence the exception... But the name is of course initialized when shown in my test case app later. What gives? Seems to me the deserialization is broken. Perhaps this is a bug in JBoss remoting, but since I can only get this with the Entity Manager I posted here. > This workaround works fine I think, but something seems terribly broken in either Hibernate or Jboss (remoting?). > public boolean equals(Object obj) { > if (name == null) return super.equals(obj); > if (obj instanceof Team) { > Team other = (Team) obj; > return other.getName().equals(this.getName()); > } > return false; > } > public int hashCode() { > if (name == null) return super.hashCode(obj); > return name.hashCode(); > } > Full stack trace of any exception that occurs: > javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) > at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) > at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:225) > at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) > at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) > at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) > at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) > Caused by: java.lang.NullPointerException > at com.weirdstuff.Player.hashCode(Player.java:83) > at java.util.HashMap.hash(HashMap.java:264) > at java.util.HashMap.put(HashMap.java:382) > at java.util.HashSet.add(HashSet.java:194) > at java.util.AbstractCollection.addAll(AbstractCollection.java:318) > at org.hibernate.collection.PersistentSet.endRead(PersistentSet.java:273) > at org.hibernate.engine.CollectionLoadContext.endLoadingCollection(CollectionLoadContext.java:183) > at org.hibernate.engine.CollectionLoadContext.endLoadingCollections(CollectionLoadContext.java:268) > at org.hibernate.engine.CollectionLoadContext.endLoadingCollections(CollectionLoadContext.java:249) > at org.hibernate.loader.Loader.endCollectionLoad(Loader.java:866) > at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:853) > at org.hibernate.loader.Loader.doQuery(Loader.java:717) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) > at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) > at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48) > at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42) > at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2821) > at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:370) > at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:351) > at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:122) > at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) > at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) > at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) > at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:839) > at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) > at org.hibernate.type.EntityType.resolve(EntityType.java:303) > at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:116) > at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842) > at org.hibernate.loader.Loader.doQuery(Loader.java:717) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) > at org.hibernate.loader.Loader.doList(Loader.java:2145) > at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029) > at org.hibernate.loader.Loader.list(Loader.java:2024) > at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:392) > at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:333) > at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) > at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) > at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) > at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:53) > at com.weirdstuff.FacadeBean.getPlayers(FacadeBean.java:17) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) > at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) > at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) > at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:225) > at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) > at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) > at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) > at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) > at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190) > at org.jboss.remoting.Client.invoke(Client.java:525) > at org.jboss.remoting.Client.invoke(Client.java:488) > at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) > at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) > at $Proxy0.getPlayers(Unknown Source) > at com.weirdstuff.TestHashCodeClient.testGetPlayer(TestHashCodeClient.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-283) Ejb3Configuration can't read Jar file OC4J

by Roman Legat (JIRA)

Ejb3Configuration can't read Jar file OC4J ------------------------------------------- Key: EJB-283 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-283 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: EM 3.3.1.GA, Core 3.2.0 GA Reporter: Roman Legat Priority: Minor The "Find-the-entities-yourself"-Feature doesn't work with OC4J, since walking over the jar fails. This is similar to #174, but the problem is not in JarVisitor, but in org.jboss.util.file.ArchiveBrowser.getBrowser: When deploying to OC4J, the Jar URLs start with "code-source" instead of "file" (See PU root URL below for example). Hence the Archive-Browser throws a RuntimeException. Solution should be similar as in #174. 2007-04-01 22:13:38,390 DEBUG Ejb3Configuration - Processing PersistenceUnitInfo [ name: MyService persistence provider classname: org.hibernate.ejb.HibernatePersistence classloader: mis_client.web.mis_client:0.0.0 Temporary classloader: org.springframework.instrument.classloading.SimpleThrowawayClassLoader@106ef07 excludeUnlistedClasses: false JTA datasource: null Non JTA datasource: org.springframework.jdbc.datasource.DriverManagerDataSource@36eb76 Transaction type: RESOURCE_LOCAL PU root URL: code-source:/C:/Programs/dev/oracle/jdev-10132/j2ee/home/applications/mis_client/mis_client/WEB-INF/lib/mis_model.jar!/ Jar files URLs [] Managed classes names [] Mapping files names [] Properties [] java.lang.RuntimeException: error trying to scan <jar-file>: code-source:/C:/Programs/dev/oracle/jdev-10132/j2ee/home/applications/mis_client/mis_client/WEB-INF/lib/mis_model.jar!/ at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:635) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:350) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) ... Caused by: java.lang.RuntimeException: Archive browser cannot handle protocol: code-source:/C:/Programs/dev/oracle/jdev-10132/j2ee/home/applications/mis_client/mis_client/WEB-INF/lib/mis_model.jar!/ at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:93) Regards, Roman -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Resolved: (EJB-30) Using jboss archive browsing for consistency

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-30?page=com... ] Emmanuel Bernard resolved EJB-30. --------------------------------- Assignee: (was: Bill Burke) Resolution: Duplicate Done the other way around. JarVisitor now takes care of everything > Using jboss archive browsing for consistency > -------------------------------------------- > > Key: EJB-30 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-30 > Project: Hibernate Entity Manager > Issue Type: Task > Components: EntityManager > Reporter: Bill Burke > > Well we should merge my code and ArchiveBrower, I made some optimization to reduce the parsing redundencies -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-325) Any PersistenceExceptions should state which persistenceunit they are from

by Max Rydahl Andersen (JIRA)

Any PersistenceExceptions should state which persistenceunit they are from -------------------------------------------------------------------------- Key: EJB-325 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-325 Project: Hibernate Entity Manager Issue Type: New Feature Affects Versions: 3.3.2.Beta1 Reporter: Max Rydahl Andersen Fix For: 3.3.2.ga example from booting seam with multiple persistence.xml's in play: FAILED CONFIGURATION: @BeforeClass init javax.persistence.PersistenceException: org.hibernate.HibernateException: Hibernate Dialect must be explicitly set at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:698) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:121) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:51) at org.jboss.seam.persistence.EntityManagerFactory.createEntityManagerFactory(EntityManagerFactory.java:85) at org.jboss.seam.persistence.EntityManagerFactory.startup(EntityManagerFactory.java:50) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2082) at org.jboss.seam.Component.callCreateMethod(Component.java:1997) at org.jboss.seam.Component.newInstance(Component.java:1968) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278) at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:95) at org.jboss.seam.init.Initialization.init(Initialization.java:555) at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:939) at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) Caused by: org.hibernate.HibernateException: Hibernate Dialect must be explicitly set at org.hibernate.dialect.DialectFactory.determineDialect(DialectFactory.java:57) at org.hibernate.dialect.DialectFactory.buildDialect(DialectFactory.java:39) at org.hibernate.cfg.SettingsFactory.determineDialect(SettingsFactory.java:409) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:119) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2006) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1289) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:691) ... 41 more ... Removed 26 stack frames No context whatsoever on what persistence unit out of 2 that is the culrpit. javax.persistence.PersistenceException: [test1unit] org.hibernate.HibernateException: Hibernate Dialect must be explicitly set would have saved me alot of time ,) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (EJB-326) Persistence unit root in a WAR not properly handled

by Emmanuel Bernard (JIRA)

Persistence unit root in a WAR not properly handled --------------------------------------------------- Key: EJB-326 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-326 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.Beta1 Reporter: Emmanuel Bernard Fix For: 3.3.2.ga jar:mywar.war!/WEB-INF/classes/ should be a valid point a valid input See Carlo's comment " I've changed the way EJB 3 submits the persistence root url to Hibernate. See http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas?view=rev&revision=67653 . " http://www.jboss.com/index.html?module=bb&op=viewtopic&t=124223&postdays=... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3061) New TimesTen7Dialect class for Oracle TimesTen In-Memory Database v 7.x

by Jason Feldhaus (JIRA)

New TimesTen7Dialect class for Oracle TimesTen In-Memory Database v 7.x ----------------------------------------------------------------------- Key: HHH-3061 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3061 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5.ga, TimesTen 7.0.4 Reporter: Jason Feldhaus Priority: Minor Attachments: TimesTen7Dialect.zip A new TimesTen dialect class has been developed for TimesTen version 7.x releases. This dialect reflects all of the SQL improvements made to the TimesTen product since the original TimesTenDialect class was developed for Hibernate several years ago. After consulting with Steve Ebersole, our ultimate goal is to have this new TimesTen7Dialect class be included in the official Hibernate distribution. The attached zip file contains the following: 1. TimesTen7Dialect.java (A new dialect class for use with TimesTen version 7.x releases) 2. ChangeLog.txt (A list of changes in relation to the original TimesTenDialect currently included in the Hibernate distribution) 3. Hibernate TimesTen7Dialect Test Results.xls (A spreadsheet describing the reasons for test case failures when running this new dialect class with the Hibernate test suite.) Please direct any questions to Jason Feldhaus (jason.feldhaus(a)oracle.com). Thank you, Jason -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2008