hibernate-issues Mailing List for Hibernate (Page 752)

An object relational-mapping (ORM) library for Java

Brought to you by: davidedalto, dreab8, epbernard, gsmet, and 5 others

hibernate-issues — Hibernate JIRA Notifications

You can subscribe to this list here.

2003	Jan	Feb	Mar	Apr	May (32)	Jun (175)	Jul (209)	Aug (302)	Sep (287)	Oct (339)	Nov (314)	Dec (329)
2004	Jan (479)	Feb (389)	Mar (599)	Apr (307)	May (390)	Jun (300)	Jul (410)	Aug (458)	Sep (299)	Oct (315)	Nov (363)	Dec (529)
2005	Jan (568)	Feb (434)	Mar (1004)	Apr (823)	May (767)	Jun (763)	Jul (854)	Aug (862)	Sep (560)	Oct (853)	Nov (763)	Dec (731)
2006	Jan (776)	Feb (608)	Mar (657)	Apr (424)	May (559)	Jun (440)	Jul (448)	Aug (58)	Sep	Oct (17)	Nov (16)	Dec (8)
2007	Jan (1)	Feb (8)	Mar (2)	Apr (5)	May (3)	Jun (3)	Jul (3)	Aug (16)	Sep (10)	Oct (4)	Nov (4)	Dec (4)
2008	Jan (8)	Feb (1)	Mar (1)	Apr	May	Jun	Jul	Aug	Sep (1)	Oct	Nov	Dec
2009	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (1)	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 750 751 752 753 754 .. 792 > >> (Page 752 of 792)

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-47) Clustered Read/Write Caching

From: <leg...@at...> - 2003-10-02 19:17:22

The following issue has been updated:

    Updater: Jason Carreira (mailto:jas...@no...)
       Date: Thu, 2 Oct 2003 2:16 PM
    Changes:
             Attachment changed to swarmcache-1.0RC2.jar
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-47
    Summary:  Clustered Read/Write Caching
       Type: Patch

     Status: Assigned
   Priority: Critical

    Project: Hibernate2
   Fix Fors:
             2.1

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:30 AM
    Updated: Thu, 2 Oct 2003 2:16 PM

Description:
Clustered Read/Write Caching
This patch adds the ability to do read-write caching in 
a clustered environment. This is accomplished by way of 
the SwarmCache caching engine. It in turn uses 
Javagroups to implement efficient, multicast-based 
cache communication. You can read a detailed 
description of SwarmCache at http://swarmcache.sf.net. 
Included in the patch is a readme that explains how it 
works and how to apply it. 

John Watkinson 

http://sourceforge.net/tracker/index.php?func=detail&aid=722039&group_id=40712&atid=428710




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-47) Clustered Read/Write Caching

From: <leg...@at...> - 2003-10-02 19:12:21

The following issue has been updated:

    Updater: Jason Carreira (mailto:jas...@no...)
       Date: Thu, 2 Oct 2003 2:12 PM
    Changes:
             Attachment changed to javagroups-all.jar
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-47
    Summary:  Clustered Read/Write Caching
       Type: Patch

     Status: Assigned
   Priority: Critical

    Project: Hibernate2
   Fix Fors:
             2.1

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:30 AM
    Updated: Thu, 2 Oct 2003 2:12 PM

Description:
Clustered Read/Write Caching
This patch adds the ability to do read-write caching in 
a clustered environment. This is accomplished by way of 
the SwarmCache caching engine. It in turn uses 
Javagroups to implement efficient, multicast-based 
cache communication. You can read a detailed 
description of SwarmCache at http://swarmcache.sf.net. 
Included in the patch is a readme that explains how it 
works and how to apply it. 

John Watkinson 

http://sourceforge.net/tracker/index.php?func=detail&aid=722039&group_id=40712&atid=428710




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-47) Clustered Read/Write Caching

From: <leg...@at...> - 2003-10-02 11:51:21

The following comment has been added to this issue:

     Author: Gavin King
    Created: Thu, 2 Oct 2003 6:50 AM
       Body:
What is the current status of this patch? Do we have a working provider for 2.1 yet?
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-47
    Summary:  Clustered Read/Write Caching
       Type: Patch

     Status: Assigned
   Priority: Critical

    Project: Hibernate2
   Fix Fors:
             2.1

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:30 AM
    Updated: Wed, 17 Sep 2003 9:52 AM

Description:
Clustered Read/Write Caching
This patch adds the ability to do read-write caching in 
a clustered environment. This is accomplished by way of 
the SwarmCache caching engine. It in turn uses 
Javagroups to implement efficient, multicast-based 
cache communication. You can read a detailed 
description of SwarmCache at http://swarmcache.sf.net. 
Included in the patch is a readme that explains how it 
works and how to apply it. 

John Watkinson 

http://sourceforge.net/tracker/index.php?func=detail&aid=722039&group_id=40712&atid=428710




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-377) Hibernate 2.1 appears to break jcs caching

From: <leg...@at...> - 2003-10-02 11:49:22

The following comment has been added to this issue:

     Author: Gavin King
    Created: Thu, 2 Oct 2003 6:48 AM
       Body:
This is useless w/o a test case.

(obviously JCS caching is not completely broken, since it works in the test suite .... so I need a simple main() method to reproduce your problem)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-377


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-377
    Summary: Hibernate 2.1 appears to break jcs caching
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: 
   Reporter: tekno

    Created: Thu, 2 Oct 2003 4:34 AM
    Updated: Thu, 2 Oct 2003 4:34 AM
Environment: Development Windows 2000 SP3, JSDK 4.1.2
Deployment Solaris 9
Database Postgresql 7.3

Description:
I am getting an AssertionFailure - cannot cache a reference to an object with a null id when I try to do an update. Here is the sample code -

NB: This has been working fine for me in hibernate versions 2.0 - 2.03

I have the following two mappings

<class name="Customer" table="customers" polymorphism="explicit">

<cache usage="read-write"/>

<id name="id" unsaved-value="0">
<generator class="sequence">
<param name="sequence">customers_id_seq</param>
</generator>
</id>

<property name="postcode"/>
<many-to-one name="csOwner" class="Employee" column="cs_owner" />
</class>

and

<class name="Employee" table="staff">

<id name="id">
<generator class="sequence">
<param name="sequence">staff_id_seq</param>
</generator>
</id>

<property name="name"/>
</class>

the following main() throws the exception

Session session = null;
Customer customer = null;
SessionFactory factory = null;
try {
// build factory
factory = new Configuration().configure().buildSessionFactory();

System.out.println("Starting first session");
// first session gets customer instance
session = factory.openSession();
customer = (Customer) session.load(Customer.class, new Long(1275));
System.out.println("Loaded customer " + customer.getId() + " has owner " + customer.getCsOwner().getId());
session.flush();
session.connection().commit();
session.close();
System.out.println("Updating address field");
// update a field
customer.setPostcode("TESTING");
System.out.println("Starting second session");
// second session persists update
session = factory.openSession();
session.update(customer);
session.flush();
session.connection().commit();
session.close();

System.out.println("Finished");
factory.close();
} catch (Exception ex){
ex.printStackTrace();
} finally {
if(session!=null)session.close();
if(factory!=null)factory.close();
System.exit(0);
}

If i remove the cache entry in the customer mapping everything is OK, but other wise i get

net.sf.hibernate.AssertionFailure: cannot cache a reference to an object with a null id
at net.sf.hibernate.type.EntityType.disassemble(EntityType.java:89)
at net.sf.hibernate.impl.CacheEntry.disassemble(CacheEntry.java:36)
at net.sf.hibernate.impl.CacheEntry.<init>(CacheEntry.java:27)
at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:42)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2278)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2235)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2178)
at com.lab.model.HibBug.main(HibBug.java:46)


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-377) Hibernate 2.1 appears to break jcs caching

From: <leg...@at...> - 2003-10-02 09:34:20

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-377


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-377
    Summary: Hibernate 2.1 appears to break jcs caching
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1

   Assignee: 
   Reporter: tekno

    Created: Thu, 2 Oct 2003 4:34 AM
    Updated: Thu, 2 Oct 2003 4:34 AM
Environment: Development Windows 2000 SP3, JSDK 4.1.2
Deployment Solaris 9
Database Postgresql 7.3

Description:
I am getting an AssertionFailure - cannot cache a reference to an object with a null id when I try to do an update. Here is the sample code -

NB: This has been working fine for me in hibernate versions 2.0 - 2.03

I have the following two mappings

<class name="Customer" table="customers" polymorphism="explicit">

<cache usage="read-write"/>

<id name="id" unsaved-value="0">
<generator class="sequence">
<param name="sequence">customers_id_seq</param>
</generator>
</id>

<property name="postcode"/>
<many-to-one name="csOwner" class="Employee" column="cs_owner" />
</class>

and

<class name="Employee" table="staff">

<id name="id">
<generator class="sequence">
<param name="sequence">staff_id_seq</param>
</generator>
</id>

<property name="name"/>
</class>

the following main() throws the exception

Session session = null;
Customer customer = null;
SessionFactory factory = null;
try {
// build factory
factory = new Configuration().configure().buildSessionFactory();

System.out.println("Starting first session");
// first session gets customer instance
session = factory.openSession();
customer = (Customer) session.load(Customer.class, new Long(1275));
System.out.println("Loaded customer " + customer.getId() + " has owner " + customer.getCsOwner().getId());
session.flush();
session.connection().commit();
session.close();
System.out.println("Updating address field");
// update a field
customer.setPostcode("TESTING");
System.out.println("Starting second session");
// second session persists update
session = factory.openSession();
session.update(customer);
session.flush();
session.connection().commit();
session.close();

System.out.println("Finished");
factory.close();
} catch (Exception ex){
ex.printStackTrace();
} finally {
if(session!=null)session.close();
if(factory!=null)factory.close();
System.exit(0);
}

If i remove the cache entry in the customer mapping everything is OK, but other wise i get

net.sf.hibernate.AssertionFailure: cannot cache a reference to an object with a null id
at net.sf.hibernate.type.EntityType.disassemble(EntityType.java:89)
at net.sf.hibernate.impl.CacheEntry.disassemble(CacheEntry.java:36)
at net.sf.hibernate.impl.CacheEntry.<init>(CacheEntry.java:27)
at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:42)
at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2278)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2235)
at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2178)
at com.lab.model.HibBug.main(HibBug.java:46)


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-367) JCSCache.put java.lang.Error: update: last is null!

From: <leg...@at...> - 2003-10-01 16:29:20

The following comment has been added to this issue:

     Author: John Kristian
    Created: Wed, 1 Oct 2003 11:28 AM
       Body:
Specifically, this problem doesn't occur if the implementation of Interceptor.instantiate sets the identifier property of the Object it returns from the second (Serializable) parameter to instantiate.

Assuming y'all expect Interceptor.instantiate to behave this way, please document your expectation in (at least) the javadoc for Interceptor.instantiate.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-367


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-367
    Summary: JCSCache.put java.lang.Error: update: last is null!
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: WON'T FIX

    Project: Hibernate2
   Versions:
             2.1 beta 3

   Assignee: 
   Reporter: John Kristian

    Created: Fri, 26 Sep 2003 4:15 PM
    Updated: Wed, 1 Oct 2003 4:33 AM
Environment: Windows XP, Microsoft SQL Server

Description:
With Hibernate `cvs checkout -r v21branch` (but not 2.0.2), the following errors occur.

14:05:11,046 ERROR [org.apache.jcs.engine.memory.lru.LRUMemoryCache] verifycache: map does NOT contain key, what the HECK!
14:05:11,046 ERROR [com.docent.lms.entities.tests.hibernate.Scan] testScan failed
java.lang.Error: update: last is null!
	at org.apache.jcs.engine.memory.lru.LRUMemoryCache.update(LRUMemoryCache.java:140)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:241)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:200)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:311)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:279)
	at net.sf.hibernate.cache.JCSCache.put(JCSCache.java:34)
	at net.sf.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:86)
	at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:2191)
	at net.sf.hibernate.loader.Loader.doResultSet(Loader.java:216)
	at net.sf.hibernate.loader.Loader.doFind(Loader.java:111)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:664)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:679)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:52)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:44)
	at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:424)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2115)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.assemble(EntityType.java:113)
	at net.sf.hibernate.collection.Set.<init>(Set.java:94)
	at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
	at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:371)
	at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:67)
	at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:184)
	at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:134)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:54)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:46)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2100)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:129)
	at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:67)
	at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:87)
	at com.docent.lms.entities.tests.hibernate.Scan.scan(Scan.java:59)



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-376) Hibernate Mapping DTD does not allow meta tags under component

From: <leg...@at...> - 2003-10-01 15:59:20

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-376


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-376
    Summary: Hibernate Mapping DTD does not allow meta tags under component
       Type: Patch

     Status: Assigned
   Priority: Trivial

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: Max Rydahl Andersen
   Reporter: Hunter Kelly

    Created: Wed, 1 Oct 2003 10:54 AM
    Updated: Wed, 1 Oct 2003 10:57 AM
Environment: Not applicable

Description:
The <component> element under <class> does not allow meta tags, for
example:

    <component name="foo" class="eg.Foo">
        <meta attribute="generated-class">eg.FooBase</meta>
        <property name="value" type="int"/>
        <property name="lastDate" type="timestamp"/>
    </component>

However, the hbm2java guy will generate classes for components, so it is necessary to be able to override stuff using the meta tags.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-376) Hibernate Mapping DTD does not allow meta tags under component

From: <leg...@at...> - 2003-10-01 15:57:21

The following issue has been updated:

    Updater: Hunter Kelly (mailto:re...@ei...)
       Date: Wed, 1 Oct 2003 10:55 AM
    Comment:
Here is a patch that stops Hibernate from complaining meta tags under component tags.
    Changes:
             Attachment changed to hibernate-mapping.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-376&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-376


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-376
    Summary: Hibernate Mapping DTD does not allow meta tags under component
       Type: Patch

     Status: Unassigned
   Priority: Trivial

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Hunter Kelly

    Created: Wed, 1 Oct 2003 10:54 AM
    Updated: Wed, 1 Oct 2003 10:55 AM
Environment: Not applicable

Description:
The <component> element under <class> does not allow meta tags, for
example:

    <component name="foo" class="eg.Foo">
        <meta attribute="generated-class">eg.FooBase</meta>
        <property name="value" type="int"/>
        <property name="lastDate" type="timestamp"/>
    </component>

However, the hbm2java guy will generate classes for components, so it is necessary to be able to override stuff using the meta tags.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-376) Hibernate Mapping DTD does not allow meta tags under component

From: <leg...@at...> - 2003-10-01 15:55:20

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-376


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-376
    Summary: Hibernate Mapping DTD does not allow meta tags under component
       Type: Patch

     Status: Unassigned
   Priority: Trivial

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Hunter Kelly

    Created: Wed, 1 Oct 2003 10:54 AM
    Updated: Wed, 1 Oct 2003 10:54 AM
Environment: Not applicable

Description:
The <component> element under <class> does not allow meta tags, for
example:

    <component name="foo" class="eg.Foo">
        <meta attribute="generated-class">eg.FooBase</meta>
        <property name="value" type="int"/>
        <property name="lastDate" type="timestamp"/>
    </component>

However, the hbm2java guy will generate classes for components, so it is necessary to be able to override stuff using the meta tags.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-372) hbm2java generates two default constructors

From: <leg...@at...> - 2003-10-01 15:47:20

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Wed, 1 Oct 2003 10:47 AM
       Body:
try to use the hibernatext download first - if that still have the bug, please try the current cvs version.

We will soon make a new release of the hibernateext (in the next week or so)


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-372


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-372
    Summary: hbm2java generates two default constructors
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Tue, 30 Sep 2003 1:10 PM
    Updated: Tue, 30 Sep 2003 5:04 PM
Environment: Linux, w/ ant 1.5.1

Description:
The following mapping generates a class with two default constructors, and therefore compilation fails:

<hibernate-mapping>

<class name="com.foobar.db.Testing" table="test_test_test">
    <id name="id" type="string" unsaved-value="null" >
        <column name="CAT_ID" sql-type="char(32)" not-null="true"/>
        <generator class="uuid.hex"/>
    </id>
    <property name="name" type="string" not-null="true">
        <column name="NAME" sql-type="varchar(16)"/>
    </property>
</class>

</hibernate-mapping>


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-373) problem in the ReflectHelper leads to "could not find getter"

From: <leg...@at...> - 2003-10-01 15:03:20

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@in...)
       Date: Wed, 1 Oct 2003 10:02 AM
    Comment:
This is not a bug. It is known and intended functionality. Perhaps we could provide for both property naming conventions, since the JavaBeans spec seems a bit unclear on this point.
    Changes:
             type changed from Bug
             priority changed from Critical
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-373&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-373


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-373
    Summary: problem in the ReflectHelper leads to "could not find getter"
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Sherban Popescu

    Created: Wed, 1 Oct 2003 6:05 AM
    Updated: Wed, 1 Oct 2003 10:02 AM
Environment: Win 2000

Description:
If one has a variable like:
aEndTerminal

The getter/setter are generated corectly by the code generator, BUT:
Because the getter/setter changes aEndTerminal to AEndTerminal, we got
into this later on:

net.sf.hibernate.PropertyNotFoundException: Could not find a getter for aEndTerminal in class com.im.Trail 
at net.sf.hibernate.util.ReflectHelper.getGetter(ReflectHelper.java:206) 
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:571) 
at net.sf.hibernate.persister.EntityPersister.<init>(EntityPersister.java:665) 
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:29) 
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:207) 
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627) 
at com.im.Main.initHibernate(Main.java:42) 
at com.im.Main.go(Main.java:48) 
at com.im.Main.main(Main.java:35) 
Exception in thread "main

The problem is Introspector.decapitalize() 
It has a "special case" that we're hitting, quote from javadoc: 

" This normally means converting the first character from upper case to lower case, but in the (unusual) special case when there is more than one character and both the first and second characters are upper case, we leave it alone." 

I've created a copy of Introspector.decapitalize inside ReflectHelper.java without the "special case" , replaced all calls to Introspector.decapitalize with my new 'decapitalize' and all works like a charm. 

So in my opinion Introspector.decapitalize should not be used in the RelectHelper !!!

This kind of bug surfaces when the variable begins with one single lower case character followed by an upper case character !!

Thanks,
--sherban


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-372) hbm2java generates two default constructors

From: <leg...@at...> - 2003-10-01 14:47:21

The following comment has been added to this issue:

     Author: Les Hazlewood
    Created: Wed, 1 Oct 2003 9:45 AM
       Body:
Oops.

I realized that hbm2java is not part of the Sept 7th build (core), as it is in the tools set (extensions).

The most recent official tools release was hibernate-extensions v. 2.0, which was built June 16th, I believe.  Since my build was after that date, I'm assuming the most recent "official" version does not incorporate the bug fix I reported.

Any news?

Do I have to build the extensions from source to ensure I get the fix?

Les
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-372


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-372
    Summary: hbm2java generates two default constructors
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Tue, 30 Sep 2003 1:10 PM
    Updated: Tue, 30 Sep 2003 5:04 PM
Environment: Linux, w/ ant 1.5.1

Description:
The following mapping generates a class with two default constructors, and therefore compilation fails:

<hibernate-mapping>

<class name="com.foobar.db.Testing" table="test_test_test">
    <id name="id" type="string" unsaved-value="null" >
        <column name="CAT_ID" sql-type="char(32)" not-null="true"/>
        <generator class="uuid.hex"/>
    </id>
    <property name="name" type="string" not-null="true">
        <column name="NAME" sql-type="varchar(16)"/>
    </property>
</class>

</hibernate-mapping>


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-375) bag.equals and bag.hashcode implementation

From: <leg...@at...> - 2003-10-01 14:45:20

The following issue has been updated:

    Updater: Emmanuel Bernard (mailto:epb...@us...)
       Date: Wed, 1 Oct 2003 9:44 AM
    Comment:
diff -u old new appliable to 2.0.3
    Changes:
             Attachment changed to bag-equals-2.0.3-patch.diff
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-375&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-375


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-375
    Summary: bag.equals and bag.hashcode implementation
       Type: Patch

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Emmanuel Bernard

    Created: Wed, 1 Oct 2003 9:42 AM
    Updated: Wed, 1 Oct 2003 9:44 AM

Description:
I implements bag.equals() and bag.hashcode() conforming the bag semantic.

I did it for hibernate 2.0.3 version (can't access head right now)

To implement it on head (1.16.2.3 right now), add the equals and hashcode version.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-375) bag.equals and bag.hashcode implementation

From: <leg...@at...> - 2003-10-01 14:43:20

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-375


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-375
    Summary: bag.equals and bag.hashcode implementation
       Type: Patch

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Emmanuel Bernard

    Created: Wed, 1 Oct 2003 9:42 AM
    Updated: Wed, 1 Oct 2003 9:42 AM

Description:
I implements bag.equals() and bag.hashcode() conforming the bag semantic.

I did it for hibernate 2.0.3 version (can't access head right now)

To implement it on head (1.16.2.3 right now), add the equals and hashcode version.




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-374) Wrong SQL statement with field "elementId"

From: <leg...@at...> - 2003-10-01 14:38:20

The following issue has been updated:

    Updater: Andrei Pavlenko (mailto:and...@ho...)
       Date: Wed, 1 Oct 2003 9:36 AM
    Changes:
             Attachment changed to create.table.sql
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-374
    Summary: Wrong SQL statement with field "elementId"
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Andrei Pavlenko

    Created: Wed, 1 Oct 2003 9:32 AM
    Updated: Wed, 1 Oct 2003 9:36 AM
Environment: Sybase

Description:
I have "composite-id" with two fields.
I want to create "many-to-one" reference for field "elementId" but generated by Hibernate SQL query is incorrect.

When I change column name to "elementOwnerId" it is generated correctly.

See attached files.


Wrong SQL:
select attribut0_.attributeId as attributeId, attribut0_.elementId as elementId, attribut0_.possibleAttributeValueId as possible3_, attribut0_.attributeValueFreeText as attribut4_, attribut0_.attributeId as attribut1_, attribut0_.elementId as elementId from AttributeValue attribut0_ where (attribut0_.elementId=? )and(attribut0_.attributeId=? )

Error message:
Select expression results in more than one column having same name. Column name 'elementId' is specified more than once


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-374) Wrong SQL statement with field "elementId"

From: <leg...@at...> - 2003-10-01 14:36:21

The following issue has been updated:

    Updater: Andrei Pavlenko (mailto:and...@ho...)
       Date: Wed, 1 Oct 2003 9:35 AM
    Changes:
             Attachment changed to AttributeValue.hbm.xml
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-374
    Summary: Wrong SQL statement with field "elementId"
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Andrei Pavlenko

    Created: Wed, 1 Oct 2003 9:32 AM
    Updated: Wed, 1 Oct 2003 9:35 AM
Environment: Sybase

Description:
I have "composite-id" with two fields.
I want to create "many-to-one" reference for field "elementId" but generated by Hibernate SQL query is incorrect.

When I change column name to "elementOwnerId" it is generated correctly.

See attached files.


Wrong SQL:
select attribut0_.attributeId as attributeId, attribut0_.elementId as elementId, attribut0_.possibleAttributeValueId as possible3_, attribut0_.attributeValueFreeText as attribut4_, attribut0_.attributeId as attribut1_, attribut0_.elementId as elementId from AttributeValue attribut0_ where (attribut0_.elementId=? )and(attribut0_.attributeId=? )

Error message:
Select expression results in more than one column having same name. Column name 'elementId' is specified more than once


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-374) Wrong SQL statement with field "elementId"

From: <leg...@at...> - 2003-10-01 14:33:20

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-374


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-374
    Summary: Wrong SQL statement with field "elementId"
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Andrei Pavlenko

    Created: Wed, 1 Oct 2003 9:32 AM
    Updated: Wed, 1 Oct 2003 9:32 AM
Environment: Sybase

Description:
I have "composite-id" with two fields.
I want to create "many-to-one" reference for field "elementId" but generated by Hibernate SQL query is incorrect.

When I change column name to "elementOwnerId" it is generated correctly.

See attached files.


Wrong SQL:
select attribut0_.attributeId as attributeId, attribut0_.elementId as elementId, attribut0_.possibleAttributeValueId as possible3_, attribut0_.attributeValueFreeText as attribut4_, attribut0_.attributeId as attribut1_, attribut0_.elementId as elementId from AttributeValue attribut0_ where (attribut0_.elementId=? )and(attribut0_.attributeId=? )

Error message:
Select expression results in more than one column having same name. Column name 'elementId' is specified more than once


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-372) hbm2java generates two default constructors

From: <leg...@at...> - 2003-10-01 14:18:22

The following comment has been added to this issue:

     Author: Les Hazlewood
    Created: Wed, 1 Oct 2003 9:17 AM
       Body:
Sorry Max, I should have clarified...

It was done via a custom build from source of 2.1 beta I pulled and compiled on August 25th. 

Apparently, 2.1 beta 3 has been released on Sourceforge's download page. (which has a date of September 7th).  Does that version fix the problem?

If so, please close the issue...

Thanks,

Les
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-372


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-372
    Summary: hbm2java generates two default constructors
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Tue, 30 Sep 2003 1:10 PM
    Updated: Tue, 30 Sep 2003 5:04 PM
Environment: Linux, w/ ant 1.5.1

Description:
The following mapping generates a class with two default constructors, and therefore compilation fails:

<hibernate-mapping>

<class name="com.foobar.db.Testing" table="test_test_test">
    <id name="id" type="string" unsaved-value="null" >
        <column name="CAT_ID" sql-type="char(32)" not-null="true"/>
        <generator class="uuid.hex"/>
    </id>
    <property name="name" type="string" not-null="true">
        <column name="NAME" sql-type="varchar(16)"/>
    </property>
</class>

</hibernate-mapping>


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-372) hbm2java generates two default constructors

From: <leg...@at...> - 2003-10-01 13:58:21

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Wed, 1 Oct 2003 8:57 AM
       Body:
What version is this happening in ?

It was a bug at some point - but should be fixed.

Please respond in what version you are running this.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-372


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-372
    Summary: hbm2java generates two default constructors
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Tue, 30 Sep 2003 1:10 PM
    Updated: Tue, 30 Sep 2003 5:04 PM
Environment: Linux, w/ ant 1.5.1

Description:
The following mapping generates a class with two default constructors, and therefore compilation fails:

<hibernate-mapping>

<class name="com.foobar.db.Testing" table="test_test_test">
    <id name="id" type="string" unsaved-value="null" >
        <column name="CAT_ID" sql-type="char(32)" not-null="true"/>
        <generator class="uuid.hex"/>
    </id>
    <property name="name" type="string" not-null="true">
        <column name="NAME" sql-type="varchar(16)"/>
    </property>
</class>

</hibernate-mapping>


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-373) problem in the ReflectHelper leads to "could not find getter"

From: <leg...@at...> - 2003-10-01 11:05:20

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-373


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-373
    Summary: problem in the ReflectHelper leads to "could not find getter"
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Sherban Popescu

    Created: Wed, 1 Oct 2003 6:05 AM
    Updated: Wed, 1 Oct 2003 6:05 AM
Environment: Win 2000

Description:
If one has a variable like:
aEndTerminal

The getter/setter are generated corectly by the code generator, BUT:
Because the getter/setter changes aEndTerminal to AEndTerminal, we got
into this later on:

net.sf.hibernate.PropertyNotFoundException: Could not find a getter for aEndTerminal in class com.im.Trail 
at net.sf.hibernate.util.ReflectHelper.getGetter(ReflectHelper.java:206) 
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:571) 
at net.sf.hibernate.persister.EntityPersister.<init>(EntityPersister.java:665) 
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:29) 
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:207) 
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627) 
at com.im.Main.initHibernate(Main.java:42) 
at com.im.Main.go(Main.java:48) 
at com.im.Main.main(Main.java:35) 
Exception in thread "main

The problem is Introspector.decapitalize() 
It has a "special case" that we're hitting, quote from javadoc: 

" This normally means converting the first character from upper case to lower case, but in the (unusual) special case when there is more than one character and both the first and second characters are upper case, we leave it alone." 

I've created a copy of Introspector.decapitalize inside ReflectHelper.java without the "special case" , replaced all calls to Introspector.decapitalize with my new 'decapitalize' and all works like a charm. 

So in my opinion Introspector.decapitalize should not be used in the RelectHelper !!!

This kind of bug surfaces when the variable begins with one single lower case character followed by an upper case character !!

Thanks,
--sherban


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-367) JCSCache.put java.lang.Error: update: last is null!

From: <leg...@at...> - 2003-10-01 09:33:19

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 1 Oct 2003 4:33 AM

This was fixed by a correct Interceptor.instantiate() implementation, according to a post on the devel list.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-367


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-367
    Summary: JCSCache.put java.lang.Error: update: last is null!
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: WON'T FIX

    Project: Hibernate2
   Versions:
             2.1 beta 3

   Assignee: 
   Reporter: John Kristian

    Created: Fri, 26 Sep 2003 4:15 PM
    Updated: Wed, 1 Oct 2003 4:33 AM
Environment: Windows XP, Microsoft SQL Server

Description:
With Hibernate `cvs checkout -r v21branch` (but not 2.0.2), the following errors occur.

14:05:11,046 ERROR [org.apache.jcs.engine.memory.lru.LRUMemoryCache] verifycache: map does NOT contain key, what the HECK!
14:05:11,046 ERROR [com.docent.lms.entities.tests.hibernate.Scan] testScan failed
java.lang.Error: update: last is null!
	at org.apache.jcs.engine.memory.lru.LRUMemoryCache.update(LRUMemoryCache.java:140)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:241)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:200)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:311)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:279)
	at net.sf.hibernate.cache.JCSCache.put(JCSCache.java:34)
	at net.sf.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:86)
	at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:2191)
	at net.sf.hibernate.loader.Loader.doResultSet(Loader.java:216)
	at net.sf.hibernate.loader.Loader.doFind(Loader.java:111)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:664)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:679)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:52)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:44)
	at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:424)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2115)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.assemble(EntityType.java:113)
	at net.sf.hibernate.collection.Set.<init>(Set.java:94)
	at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
	at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:371)
	at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:67)
	at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:184)
	at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:134)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:54)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:46)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2100)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:129)
	at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:67)
	at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:87)
	at com.docent.lms.entities.tests.hibernate.Scan.scan(Scan.java:59)



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-367) JCSCache.put java.lang.Error: update: last is null!

From: <leg...@at...> - 2003-09-30 22:45:20

The following issue has been updated:

    Updater: John Kristian (mailto:jkr...@do...)
       Date: Tue, 30 Sep 2003 5:45 PM
    Comment:
test5.zip (attached) exhibits lost entries in Role.associations.  To produce this symptom, I added 'unique' attributes to the Role.name and Permission.code columns (which I guess affects the ordering of query results).
    Changes:
             Attachment changed to test5.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-367&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-367


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-367
    Summary: JCSCache.put java.lang.Error: update: last is null!
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1 beta 3

   Assignee: 
   Reporter: John Kristian

    Created: Fri, 26 Sep 2003 4:15 PM
    Updated: Tue, 30 Sep 2003 5:45 PM
Environment: Windows XP, Microsoft SQL Server

Description:
With Hibernate `cvs checkout -r v21branch` (but not 2.0.2), the following errors occur.

14:05:11,046 ERROR [org.apache.jcs.engine.memory.lru.LRUMemoryCache] verifycache: map does NOT contain key, what the HECK!
14:05:11,046 ERROR [com.docent.lms.entities.tests.hibernate.Scan] testScan failed
java.lang.Error: update: last is null!
	at org.apache.jcs.engine.memory.lru.LRUMemoryCache.update(LRUMemoryCache.java:140)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:241)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:200)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:311)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:279)
	at net.sf.hibernate.cache.JCSCache.put(JCSCache.java:34)
	at net.sf.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:86)
	at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:2191)
	at net.sf.hibernate.loader.Loader.doResultSet(Loader.java:216)
	at net.sf.hibernate.loader.Loader.doFind(Loader.java:111)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:664)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:679)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:52)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:44)
	at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:424)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2115)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.assemble(EntityType.java:113)
	at net.sf.hibernate.collection.Set.<init>(Set.java:94)
	at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
	at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:371)
	at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:67)
	at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:184)
	at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:134)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:54)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:46)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2100)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:129)
	at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:67)
	at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:87)
	at com.docent.lms.entities.tests.hibernate.Scan.scan(Scan.java:59)



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-372) hbm2java generates two default constructors

From: <leg...@at...> - 2003-09-30 22:05:21

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Tue, 30 Sep 2003 5:04 PM
    Comment:
yours, Max
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-372


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-372
    Summary: hbm2java generates two default constructors
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Tue, 30 Sep 2003 1:10 PM
    Updated: Tue, 30 Sep 2003 5:04 PM
Environment: Linux, w/ ant 1.5.1

Description:
The following mapping generates a class with two default constructors, and therefore compilation fails:

<hibernate-mapping>

<class name="com.foobar.db.Testing" table="test_test_test">
    <id name="id" type="string" unsaved-value="null" >
        <column name="CAT_ID" sql-type="char(32)" not-null="true"/>
        <generator class="uuid.hex"/>
    </id>
    <property name="name" type="string" not-null="true">
        <column name="NAME" sql-type="varchar(16)"/>
    </property>
</class>

</hibernate-mapping>


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-372) hbm2java generates two default constructors

From: <leg...@at...> - 2003-09-30 18:11:30

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-372


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-372
    Summary: hbm2java generates two default constructors
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: 
   Reporter: Les Hazlewood

    Created: Tue, 30 Sep 2003 1:10 PM
    Updated: Tue, 30 Sep 2003 1:10 PM
Environment: Linux, w/ ant 1.5.1

Description:
The following mapping generates a class with two default constructors, and therefore compilation fails:

<hibernate-mapping>

<class name="com.foobar.db.Testing" table="test_test_test">
    <id name="id" type="string" unsaved-value="null" >
        <column name="CAT_ID" sql-type="char(32)" not-null="true"/>
        <generator class="uuid.hex"/>
    </id>
    <property name="name" type="string" not-null="true">
        <column name="NAME" sql-type="varchar(16)"/>
    </property>
</class>

</hibernate-mapping>


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-367) JCSCache.put java.lang.Error: update: last is null!

From: <leg...@at...> - 2003-09-30 18:05:20

The following issue has been updated:

    Updater: John Kristian (mailto:jkr...@do...)
       Date: Tue, 30 Sep 2003 1:05 PM
    Comment:
test4.zip (attached) exhibits the problem using test data created via Hibernate.  Surprisingly, Scan.java does not find any lost members of Role.associations, using these test data.
    Changes:
             Attachment changed to test4.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-367&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-367


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-367
    Summary: JCSCache.put java.lang.Error: update: last is null!
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1 beta 3

   Assignee: 
   Reporter: John Kristian

    Created: Fri, 26 Sep 2003 4:15 PM
    Updated: Tue, 30 Sep 2003 1:05 PM
Environment: Windows XP, Microsoft SQL Server

Description:
With Hibernate `cvs checkout -r v21branch` (but not 2.0.2), the following errors occur.

14:05:11,046 ERROR [org.apache.jcs.engine.memory.lru.LRUMemoryCache] verifycache: map does NOT contain key, what the HECK!
14:05:11,046 ERROR [com.docent.lms.entities.tests.hibernate.Scan] testScan failed
java.lang.Error: update: last is null!
	at org.apache.jcs.engine.memory.lru.LRUMemoryCache.update(LRUMemoryCache.java:140)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:241)
	at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:200)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:311)
	at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:279)
	at net.sf.hibernate.cache.JCSCache.put(JCSCache.java:34)
	at net.sf.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:86)
	at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:2191)
	at net.sf.hibernate.loader.Loader.doResultSet(Loader.java:216)
	at net.sf.hibernate.loader.Loader.doFind(Loader.java:111)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:664)
	at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:679)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:52)
	at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:44)
	at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:424)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2115)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.assemble(EntityType.java:113)
	at net.sf.hibernate.collection.Set.<init>(Set.java:94)
	at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
	at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:371)
	at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:67)
	at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:184)
	at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:134)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:54)
	at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:46)
	at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:2100)
	at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1977)
	at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1936)
	at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:76)
	at net.sf.hibernate.type.EntityType.nullSafeGet(EntityType.java:129)
	at net.sf.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:67)
	at net.sf.hibernate.impl.IteratorImpl.next(IteratorImpl.java:87)
	at com.docent.lms.entities.tests.hibernate.Scan.scan(Scan.java:59)



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

93 messages has been excluded from this view by a project administrator.

Flat | Threaded

<< < 1 .. 750 751 752 753 754 .. 792 > >> (Page 752 of 792)