hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-485) DYNAMIC_PREPARE and @@identity

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Thu, 20 Nov 2003 7:38 PM
       Body:
I'm not quite sure what you are trying to tell us here....
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-485
    Summary: DYNAMIC_PREPARE and @@identity
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Richard Scranton

    Created: Thu, 20 Nov 2003 1:22 PM
    Updated: Thu, 20 Nov 2003 7:38 PM

Description:
Using the Sybase jConnect jdbc driver version 4.5 or 5.5, if the connection property DYNAMIC_PREPARE is set to "true", "select @@identity" will always return a "0".  This is an artifact of the Sybase implementation of prepared statements.  Statements compiled at the server become stored procedures marked by the "DYN" token, and appear named as dyn100, dyn101, etc in the
captured TDS stream.  The value of @@identity is lost at the end of a procedure, so a sequence of prepared statements like:

insert into Yadda (val1,val2) values ( 1,2 )
select @@identity

will execute as expected when DYNAMIC_PREPARE is false.  If it is set to true, the statement "select @@identity" will return "0".  Sybase suggests something like this workaround to get the expected behavior:

String nl=System.getProperty("line.separator");
PreparedStaement ps=conn.prepareStatement(
        "insert into Yadd (val1,val2) values ( 1,2 )"
        + nl
        + "select @@identity");

Leaving DYNAMIC_PREPARE set false gives away throughput if the queries being sent and parsed are of significant size.  TDS dumps show they are being sent and parsed with each invocation.  Setting DYNAMIC_PREPARE to true allows reuse of the parsed queries.



---------------------------------------------------------------------
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-440) Direct collection property access

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Thu, 20 Nov 2003 3:13 PM
       Body:
Should there be a new attachment ? 
Can only see the original files that did not fail...
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 5

   Assignee: Max Rydahl Andersen
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Thu, 20 Nov 2003 3:13 PM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
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-485) DYNAMIC_PREPARE and @@identity

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-485
    Summary: DYNAMIC_PREPARE and @@identity
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Richard Scranton

    Created: Thu, 20 Nov 2003 1:22 PM
    Updated: Thu, 20 Nov 2003 1:22 PM

Description:
Using the Sybase jConnect jdbc driver version 4.5 or 5.5, if the connection property DYNAMIC_PREPARE is set to "true", "select @@identity" will always return a "0".  This is an artifact of the Sybase implementation of prepared statements.  Statements compiled at the server become stored procedures marked by the "DYN" token, and appear named as dyn100, dyn101, etc in the
captured TDS stream.  The value of @@identity is lost at the end of a procedure, so a sequence of prepared statements like:

insert into Yadda (val1,val2) values ( 1,2 )
select @@identity

will execute as expected when DYNAMIC_PREPARE is false.  If it is set to true, the statement "select @@identity" will return "0".  Sybase suggests something like this workaround to get the expected behavior:

String nl=System.getProperty("line.separator");
PreparedStaement ps=conn.prepareStatement(
        "insert into Yadd (val1,val2) values ( 1,2 )"
        + nl
        + "select @@identity");

Leaving DYNAMIC_PREPARE set false gives away throughput if the queries being sent and parsed are of significant size.  TDS dumps show they are being sent and parsed with each invocation.  Setting DYNAMIC_PREPARE to true allows reuse of the parsed queries.



---------------------------------------------------------------------
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-484) ResultSet can not re-read row data for column 2

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Benoit Menendez
    Created: Thu, 20 Nov 2003 12:27 PM
       Body:
I hit enter a little too soon... sorry...

This problem shows up with the latest SP2 Microsoft SQL Server driver

The problem query generated by Hibernate is:

2003-11-20 09:57:48,827 INFO  [STDOUT] Hibernate: select kms_vers0_.id as id__, kms_vers0_.DOCUMENT_ID as DOCUMEN10___, kms_vers0_.id as id0_, kms_vers0_.name as name0_, kms_vers0_.description as descript3_0_, kms_vers0_.CREATED_BY as CREATED_BY0_, kms_vers0_.CREATION_TIME as CREATION5_0_, kms_vers0_.MODIFIED_BY as MODIFIED6_0_, kms_vers0_.MODIFICATION_TIME as MODIFICA7_0_, kms_vers0_.MIME_TYPE as MIME_TYPE0_, kms_vers0_.content as content0_, kms_vers0_.DOCUMENT_ID as DOCUMEN10_0_ from KMS_VERSION kms_vers0_ where kms_vers0_.DOCUMENT_ID=?

The version I use is 21beta6

details in the attached file

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-484
    Summary: ResultSet can not re-read row data for column 2
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Benoit Menendez

    Created: Thu, 20 Nov 2003 12:24 PM
    Updated: Thu, 20 Nov 2003 12:27 PM

Description:



---------------------------------------------------------------------
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-484) ResultSet can not re-read row data for column 2

[<leg...@at...>]

The following issue has been updated:

    Updater: Benoit Menendez (mailto:be...@me...)
       Date: Thu, 20 Nov 2003 12:24 PM
    Changes:
             Attachment changed to bug.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-484
    Summary: ResultSet can not re-read row data for column 2
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Benoit Menendez

    Created: Thu, 20 Nov 2003 12:24 PM
    Updated: Thu, 20 Nov 2003 12:24 PM

Description:



---------------------------------------------------------------------
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-484) ResultSet can not re-read row data for column 2

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-484
    Summary: ResultSet can not re-read row data for column 2
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Benoit Menendez

    Created: Thu, 20 Nov 2003 12:24 PM
    Updated: Thu, 20 Nov 2003 12:24 PM

Description:



---------------------------------------------------------------------
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-483) Odd behavior from query cache startup

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-483
    Summary: Odd behavior from query cache startup
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 6

   Assignee: 
   Reporter: Loren Rosen

    Created: Thu, 20 Nov 2003 12:16 PM
    Updated: Thu, 20 Nov 2003 12:16 PM
Environment: Mac OSX 10.1.5
JDK 1.3.1

Description:
It seems that it takes 3 query calls before the query cache is propery initialized and starts caching queries. I'll grant this isn't so critical for overall effectiveness of the cache, but it will confuse someone who tries to write a very simple program to demonstrate the operation of the query cache.

For example, if the gist of main() is this:
        Session sess;
        Long l = new Long(79);

        for (int i=1;i<=5;i++) {
            System.out.println("-----run query iteration " + i + " --------------");
            sess = sessions.openSession();
            runQuery(l, sess);
            sess.close();
        }

and here's the method it calls
    private static void runQuery(Long docId, Session sess) throws Exception {

        Document doc;
        Transaction tx = null;

        try {
            tx = sess.beginTransaction();
            Query q = sess.createQuery("select from Document doc where doc.id=:docId");
            q.setLong("docId", docId.longValue());
            q.setCacheable(true);
            List list = q.list();
            tx.commit();
        } catch (Exception e) {
            tx.rollback();
            throw e;
        }

    }

If you run this with query logging enabled, you'll see that only the 4th and 5th iterations of loop succeed in getting the query results from the query cache.

I've traced through the code, and I think I know what's going on. It's a bit complicated to explain, but I'll be happy to write it down if anyone wants to try fixing the problem.


---------------------------------------------------------------------
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-479) Session.replicate() does not preserve object associations

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Brian Denny
    Created: Thu, 20 Nov 2003 9:39 AM
       Body:
It's still failing.  I've reposted my test program (same URL), using hibernate2.jar built from current CVS, and with the XDoclet task removed from the build (i.e., mapping file already built).  I also tested it with a clean Ant installation.

So you should be able to "just run ant"; let me know if you have any further problems with it.


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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-479
    Summary: Session.replicate() does not preserve object associations
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1

   Assignee: 
   Reporter: Brian Denny

    Created: Tue, 18 Nov 2003 11:56 AM
    Updated: Thu, 20 Nov 2003 9:39 AM

Description:
Calling session.replicate() on a parent object with a many-to-many-mapped List of children fails to replicate the association, i.e., no rows are created in the association table, although all the objects themselves are inserted.

In order to see this bug, the objects you are trying to replicate() must have been actually load()ed from some other session; i.e., if you instantiate some objects freshly and assign ids to them and call session.replicate(), you don't see the bug.

I have created a little project with an Ant build script which demonstrates this bug.  You may download it from 

http://www.briandenny.net/hibernate_bug.tgz




---------------------------------------------------------------------
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-482) NPE in net.sf.hibernate.impl.SessionImpl

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-482
    Summary: NPE in net.sf.hibernate.impl.SessionImpl
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Michail Jekimov

    Created: Thu, 20 Nov 2003 8:50 AM
    Updated: Thu, 20 Nov 2003 8:50 AM
Environment: WinXP Professional, JDK 1.4, Tomcat 4.1.24

Description:
I get a NPE in the following method in
if (!ce.initialized)

It happens sporadically but rather often.

/**
	 * called by a collection that wants to initialize itself
	 */
	public void initialize(PersistentCollection collection, boolean writing) throws HibernateException {

		CollectionEntry ce = getCollectionEntry(collection);

		if ( !ce.initialized ) {

			if ( log.isTraceEnabled() ) log.trace( "initializing collection " + MessageHelper.infoString(ce.loadedPersister, ce.loadedKey) );

			try {
				ce.loadedPersister.getInitializer().initialize(ce.loadedKey, this);
			}
			catch (SQLException sqle) {
				throw new JDBCException("SQLException initializing collection", sqle);
			}

		}
	}



---------------------------------------------------------------------
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-33) instanceof statement

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Emmanuel Bernard
    Created: Thu, 20 Nov 2003 6:44 AM
       Body:
This can be useful for collections referencing a superclass and request using subclass properties.
Keeping the previous syntax
from A as a where ((a.super instanceof Sub1 and ((Sub1)a.super).property = ?)
  or (a.super instanceof Sub2 and ((Sub2 a.super).property2 = ?))
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-33
    Summary:  instanceof statement
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2

   Assignee: 
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:19 AM
    Updated: Thu, 20 Nov 2003 6:44 AM

Description:
instanceof statement
Suppose I have class A and class B mapped in 
Hibernate as (for example) joined-subclass: 

public class A { int id; } 
public class B extends A { String status; } 

I wish to select all objects of class A and only those 
objects of class B which have status = 'READY'. 
In current HQL I can do it as: 

select a from a in class A left outer join b in class B 
where b.status is null or b.status = 'READY'; 

but SQL for select a from a in class A already has outer 
joined subclass B and SQL becames ineffective! 
I thik it will be nice to have instanceof statements and 
type cast. So my HQL has to be looks like: 

from a in class A where ((B)a).status is null or ((B) 
a).status = 'READY'; 

or using aliases (which also doesn't works for one-to- 
many, unfortunately): 

from A as a, (B)a as b where b.status is null or b.status 
= 'READY'; 

or using instanceof statement: 

from A as a where (a instanceof A) or (a instanceof B 
and ((B)a).status = 'READY') 

Perhaps here can be anothe syntax for it. 

With best regards1 
Dmitry M.Ivlev 

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


---------------------------------------------------------------------
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-83) Query.setLockMode(alias, lockMode)

[<leg...@at...>]

The following issue has been updated:

    Updater: Gavin King (mailto:ga...@hi...)
       Date: Thu, 20 Nov 2003 12:55 AM
    Changes:
             Fix Version changed to 2.1 beta 1
             Fix Version changed from 2.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-83
    Summary: Query.setLockMode(alias, lockMode)
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 beta 1

   Assignee: Gavin King
   Reporter: Gavin King

    Created: Fri, 16 May 2003 11:29 PM
    Updated: Thu, 20 Nov 2003 12:55 AM

Description:
It would be nice to add a way of specifying FOR UPDATE OF (and Oracle FOR UPDATE OF ... NOWAIT) in a query.


---------------------------------------------------------------------
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-440) Direct collection property access

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Alexey Kaigorodov
    Created: Wed, 19 Nov 2003 11:20 PM
       Body:
A attached test case Foo in environment w2k, jdk 1.4, hibernate 2.1b6 fail. The stack trace in comment of 17/Nov/03 10:52 PM

-- 
With best regards, 
Alex
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 5

   Assignee: Max Rydahl Andersen
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Fri, 14 Nov 2003 5:23 PM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
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-479) Session.replicate() does not preserve object associations

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Wed, 19 Nov 2003 10:09 AM
       Body:
I tried to build, and it failed with an xdoclet problem.

Try again in a few hours, anonymous CVS is about 24 hours behind. If its still broken, send me a working build. ("working" means all i do is type "ant").
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-479
    Summary: Session.replicate() does not preserve object associations
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1

   Assignee: 
   Reporter: Brian Denny

    Created: Tue, 18 Nov 2003 11:56 AM
    Updated: Tue, 18 Nov 2003 11:56 AM

Description:
Calling session.replicate() on a parent object with a many-to-many-mapped List of children fails to replicate the association, i.e., no rows are created in the association table, although all the objects themselves are inserted.

In order to see this bug, the objects you are trying to replicate() must have been actually load()ed from some other session; i.e., if you instantiate some objects freshly and assign ids to them and call session.replicate(), you don't see the bug.

I have created a little project with an Ant build script which demonstrates this bug.  You may download it from 

http://www.briandenny.net/hibernate_bug.tgz




---------------------------------------------------------------------
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-481) SQL Update with alias replacement

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-481
    Summary: SQL Update with alias replacement
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: xfgdf

    Created: Wed, 19 Nov 2003 9:58 AM
    Updated: Wed, 19 Nov 2003 9:58 AM

Description:
There is currently a way to do a SQL SELECT with createSQLQuery(). It would be great to have a way to also perform SQL UPDATE and DELETE with alias replacement. It would be very helpfull to perform massive update on many rows.

The same way we have :

Query q = session.createSQLQuery(
    "SELECT {person.*} FROM PERSON {person} WHERE ROWNUM<10", 
    "person", 
    Person.class
);

To be able to do this :

session.executeSQL(
    "UPDATE {person} SET {person.name} = UPPER({person.name})"
);

   Adrien


---------------------------------------------------------------------
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-478) Foreign Key constraints duplicated with SchemaUpdate

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gerjon de Vries
    Created: Wed, 19 Nov 2003 3:05 AM
       Body:
The problem will only reproduce with mysql-connector-java-3.0.9-stable-bin (I wrote 3.0.8 in the original message by mistake).
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-478
    Summary: Foreign Key constraints duplicated with SchemaUpdate
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Gerjon de Vries

    Created: Tue, 18 Nov 2003 10:48 AM
    Updated: Tue, 18 Nov 2003 10:48 AM
Environment: MySql 4.0.16-Max, mysql-connector-java-3.0.9-stable-bin, InnoDB tables, Linux (SuSe 9.0).

Description:
When using SchemaUpdate to create/alter table definitions, each consecutive use of "SchemaUpdate(configuration).execute(true)" will regenerate all foreign key constraint commands (e.g. "ALTER TABLE X add index(fromId), add constraint FK2065BD77CB5B07 foreign key (fromId) references Y(id)"). Effectively you get duplicates for each key, which might degrade performance, and after some time cause errors, since MySql allows a limited number of FK's.

It seems to me that this is caused by a mismatch of the constraint names in net.sf.hibernate.mapping.Table and net.sf.tool.hbm2ddl.TableMetaData, but I'm not 100% sure. The "ALTER TABLE ..." is generated in Configuration.java:462.

Note that I'm using InnoDB tables (for the transaction support). Also note that the problem will only reproduce with mysql-connector-java-3.0.8-stable-bin (or newer), since older versions have a bug with requesting foreign key information on InnoDB tables.



---------------------------------------------------------------------
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-479) Session.replicate() does not preserve object associations

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Tue, 18 Nov 2003 7:05 PM
       Body:
This should now be working in current CVS. Try it out!

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-479
    Summary: Session.replicate() does not preserve object associations
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1

   Assignee: 
   Reporter: Brian Denny

    Created: Tue, 18 Nov 2003 11:56 AM
    Updated: Tue, 18 Nov 2003 11:56 AM

Description:
Calling session.replicate() on a parent object with a many-to-many-mapped List of children fails to replicate the association, i.e., no rows are created in the association table, although all the objects themselves are inserted.

In order to see this bug, the objects you are trying to replicate() must have been actually load()ed from some other session; i.e., if you instantiate some objects freshly and assign ids to them and call session.replicate(), you don't see the bug.

I have created a little project with an Ant build script which demonstrates this bug.  You may download it from 

http://www.briandenny.net/hibernate_bug.tgz




---------------------------------------------------------------------
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-480) Ant task that generates hibernate.cfg.xml

[<leg...@at...>]

The following issue has been updated:

    Updater: Per Thomas Jahr (mailto:Per...@nr...)
       Date: Tue, 18 Nov 2003 3:18 PM
    Changes:
             Attachment changed to JcsClassCache.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-480
    Summary: Ant task that generates hibernate.cfg.xml
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: 
   Reporter: Per Thomas Jahr

    Created: Tue, 18 Nov 2003 3:17 PM
    Updated: Tue, 18 Nov 2003 3:18 PM

Description:
I have written an Ant task that generates the hibernate.cfg.xml file. 

This can be usefull either as a standalone Ant task or one can write a more generic Hibernate tool and then write a Ant task for it (like hbm2java).

Background:
I use middlegen to generate all the mapping files from my database. This gives me one mapping file for each table, but middlegen does not update the hibernate.cfg.xml file.

This task will scan a directory (or filesets as it is called in Ant) and fill in the correct mappings that it finds.

Usage:

1. The class that defines the task must be defined (by using taskdef).
2. The "dest" attribute is the destination for generated config file.
3. <sfproperty name="" value=""/> is the session factory properties.
4. <mapping dir=""/> is the folder where the mapping files can be found. Note that this is a fileset so you could write something like:

<mapping dir="my_mapping_folder>
  <include name="**/*.hbm"/>
  <exclude name="**/Testtable.hbm"/>
</mapping>

<target name="updatehibernateconfig">  
  <taskdef name="hibconfig"
    classname="no.nr.ant HibernateConfigFileTask"/>  
  <hibconfig dest="hibernate.cfg.xml">    
    <sfproperty name="connection.datasource"
      value="java:comp/env/jdbc/hibernate"/>    
    <sfproperty name="show_sql" value="false"/>    
    <sfproperty name="dialect"
      value="net.sf.hibernate.dialect.SybaseDialect"/>
    <mapping dir="mapping_dir"/>
  </hibconfig>
</target>


Some limitations:
* Only "mapping resource" is supported (not jar or file). And I don't know what they mean.
* It uses the 2.0 version of the DTD (http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd). It should be designed so that it can easily support new DTD's.





---------------------------------------------------------------------
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-480) Ant task that generates hibernate.cfg.xml

[<leg...@at...>]

The following issue has been updated:

    Updater: Per Thomas Jahr (mailto:Per...@nr...)
       Date: Tue, 18 Nov 2003 3:18 PM
    Changes:
             Attachment changed to JcsCollectionCache.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-480
    Summary: Ant task that generates hibernate.cfg.xml
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: 
   Reporter: Per Thomas Jahr

    Created: Tue, 18 Nov 2003 3:17 PM
    Updated: Tue, 18 Nov 2003 3:18 PM

Description:
I have written an Ant task that generates the hibernate.cfg.xml file. 

This can be usefull either as a standalone Ant task or one can write a more generic Hibernate tool and then write a Ant task for it (like hbm2java).

Background:
I use middlegen to generate all the mapping files from my database. This gives me one mapping file for each table, but middlegen does not update the hibernate.cfg.xml file.

This task will scan a directory (or filesets as it is called in Ant) and fill in the correct mappings that it finds.

Usage:

1. The class that defines the task must be defined (by using taskdef).
2. The "dest" attribute is the destination for generated config file.
3. <sfproperty name="" value=""/> is the session factory properties.
4. <mapping dir=""/> is the folder where the mapping files can be found. Note that this is a fileset so you could write something like:

<mapping dir="my_mapping_folder>
  <include name="**/*.hbm"/>
  <exclude name="**/Testtable.hbm"/>
</mapping>

<target name="updatehibernateconfig">  
  <taskdef name="hibconfig"
    classname="no.nr.ant HibernateConfigFileTask"/>  
  <hibconfig dest="hibernate.cfg.xml">    
    <sfproperty name="connection.datasource"
      value="java:comp/env/jdbc/hibernate"/>    
    <sfproperty name="show_sql" value="false"/>    
    <sfproperty name="dialect"
      value="net.sf.hibernate.dialect.SybaseDialect"/>
    <mapping dir="mapping_dir"/>
  </hibconfig>
</target>


Some limitations:
* Only "mapping resource" is supported (not jar or file). And I don't know what they mean.
* It uses the 2.0 version of the DTD (http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd). It should be designed so that it can easily support new DTD's.





---------------------------------------------------------------------
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-480) Ant task that generates hibernate.cfg.xml

[<leg...@at...>]

The following issue has been updated:

    Updater: Per Thomas Jahr (mailto:Per...@nr...)
       Date: Tue, 18 Nov 2003 3:18 PM
    Changes:
             Attachment changed to HibernateConfigFileTask.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-480
    Summary: Ant task that generates hibernate.cfg.xml
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: 
   Reporter: Per Thomas Jahr

    Created: Tue, 18 Nov 2003 3:17 PM
    Updated: Tue, 18 Nov 2003 3:18 PM

Description:
I have written an Ant task that generates the hibernate.cfg.xml file. 

This can be usefull either as a standalone Ant task or one can write a more generic Hibernate tool and then write a Ant task for it (like hbm2java).

Background:
I use middlegen to generate all the mapping files from my database. This gives me one mapping file for each table, but middlegen does not update the hibernate.cfg.xml file.

This task will scan a directory (or filesets as it is called in Ant) and fill in the correct mappings that it finds.

Usage:

1. The class that defines the task must be defined (by using taskdef).
2. The "dest" attribute is the destination for generated config file.
3. <sfproperty name="" value=""/> is the session factory properties.
4. <mapping dir=""/> is the folder where the mapping files can be found. Note that this is a fileset so you could write something like:

<mapping dir="my_mapping_folder>
  <include name="**/*.hbm"/>
  <exclude name="**/Testtable.hbm"/>
</mapping>

<target name="updatehibernateconfig">  
  <taskdef name="hibconfig"
    classname="no.nr.ant HibernateConfigFileTask"/>  
  <hibconfig dest="hibernate.cfg.xml">    
    <sfproperty name="connection.datasource"
      value="java:comp/env/jdbc/hibernate"/>    
    <sfproperty name="show_sql" value="false"/>    
    <sfproperty name="dialect"
      value="net.sf.hibernate.dialect.SybaseDialect"/>
    <mapping dir="mapping_dir"/>
  </hibconfig>
</target>


Some limitations:
* Only "mapping resource" is supported (not jar or file). And I don't know what they mean.
* It uses the 2.0 version of the DTD (http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd). It should be designed so that it can easily support new DTD's.





---------------------------------------------------------------------
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-480) Ant task that generates hibernate.cfg.xml

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-480
    Summary: Ant task that generates hibernate.cfg.xml
       Type: Patch

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: 
   Reporter: Per Thomas Jahr

    Created: Tue, 18 Nov 2003 3:17 PM
    Updated: Tue, 18 Nov 2003 3:17 PM

Description:
I have written an Ant task that generates the hibernate.cfg.xml file. 

This can be usefull either as a standalone Ant task or one can write a more generic Hibernate tool and then write a Ant task for it (like hbm2java).

Background:
I use middlegen to generate all the mapping files from my database. This gives me one mapping file for each table, but middlegen does not update the hibernate.cfg.xml file.

This task will scan a directory (or filesets as it is called in Ant) and fill in the correct mappings that it finds.

Usage:

1. The class that defines the task must be defined (by using taskdef).
2. The "dest" attribute is the destination for generated config file.
3. <sfproperty name="" value=""/> is the session factory properties.
4. <mapping dir=""/> is the folder where the mapping files can be found. Note that this is a fileset so you could write something like:

<mapping dir="my_mapping_folder>
  <include name="**/*.hbm"/>
  <exclude name="**/Testtable.hbm"/>
</mapping>

<target name="updatehibernateconfig">  
  <taskdef name="hibconfig"
    classname="no.nr.ant HibernateConfigFileTask"/>  
  <hibconfig dest="hibernate.cfg.xml">    
    <sfproperty name="connection.datasource"
      value="java:comp/env/jdbc/hibernate"/>    
    <sfproperty name="show_sql" value="false"/>    
    <sfproperty name="dialect"
      value="net.sf.hibernate.dialect.SybaseDialect"/>
    <mapping dir="mapping_dir"/>
  </hibconfig>
</target>


Some limitations:
* Only "mapping resource" is supported (not jar or file). And I don't know what they mean.
* It uses the 2.0 version of the DTD (http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd). It should be designed so that it can easily support new DTD's.





---------------------------------------------------------------------
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-479) Session.replicate() does not preserve object associations

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-479
    Summary: Session.replicate() does not preserve object associations
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1

   Assignee: 
   Reporter: Brian Denny

    Created: Tue, 18 Nov 2003 11:56 AM
    Updated: Tue, 18 Nov 2003 11:56 AM

Description:
Calling session.replicate() on a parent object with a many-to-many-mapped List of children fails to replicate the association, i.e., no rows are created in the association table, although all the objects themselves are inserted.

In order to see this bug, the objects you are trying to replicate() must have been actually load()ed from some other session; i.e., if you instantiate some objects freshly and assign ids to them and call session.replicate(), you don't see the bug.

I have created a little project with an Ant build script which demonstrates this bug.  You may download it from 

http://www.briandenny.net/hibernate_bug.tgz




---------------------------------------------------------------------
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-478) Foreign Key constraints duplicated with SchemaUpdate

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-478
    Summary: Foreign Key constraints duplicated with SchemaUpdate
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Gerjon de Vries

    Created: Tue, 18 Nov 2003 10:48 AM
    Updated: Tue, 18 Nov 2003 10:48 AM
Environment: MySql 4.0.16-Max, mysql-connector-java-3.0.9-stable-bin, InnoDB tables, Linux (SuSe 9.0).

Description:
When using SchemaUpdate to create/alter table definitions, each consecutive use of "SchemaUpdate(configuration).execute(true)" will regenerate all foreign key constraint commands (e.g. "ALTER TABLE X add index(fromId), add constraint FK2065BD77CB5B07 foreign key (fromId) references Y(id)"). Effectively you get duplicates for each key, which might degrade performance, and after some time cause errors, since MySql allows a limited number of FK's.

It seems to me that this is caused by a mismatch of the constraint names in net.sf.hibernate.mapping.Table and net.sf.tool.hbm2ddl.TableMetaData, but I'm not 100% sure. The "ALTER TABLE ..." is generated in Configuration.java:462.

Note that I'm using InnoDB tables (for the transaction support). Also note that the problem will only reproduce with mysql-connector-java-3.0.8-stable-bin (or newer), since older versions have a bug with requesting foreign key information on InnoDB tables.



---------------------------------------------------------------------
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-440) Direct collection property access

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Tue, 18 Nov 2003 1:42 AM
       Body:
Is this a stack trace for the exact test case you provided ?

I see you write bag="..." which to me indicates it is not ;)

Would you please ensure (or re-provide) that you can make a testcase with a main class that result in the exception ?

Maybe even try to use the latest release (2.1b6)

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 5

   Assignee: Max Rydahl Andersen
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Fri, 14 Nov 2003 5:23 PM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
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-440) Direct collection property access

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Alexey Kaigorodov
    Created: Mon, 17 Nov 2003 10:52 PM
       Body:
Very strange what you don't reproduce bug.
I have it also in 2.1 beta 6.
The exception appears while loading mapping
i.e. does not depend on database.

ERROR net.sf.hibernate.cfg.Configuration  - Could not compile the mapping document
net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:102)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:956)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:949)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:312)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1146)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addClass(Configuration.java:307)
	at Foo.main(Foo.java:16)
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for bars in class Foo
	at net.sf.hibernate.property.BasicPropertyAccessor.getGetter(BasicPropertyAccessor.java:186)
	at net.sf.hibernate.util.ReflectHelper.reflectedPropertyType(ReflectHelper.java:57)
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:91)
	... 8 more
net.sf.hibernate.MappingException: Error reading resource: Foo.hbm.xml
	at net.sf.hibernate.cfg.Configuration.addClass(Configuration.java:310)
	at Foo.main(Foo.java:16)
Caused by: net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:102)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:956)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:949)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:312)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1146)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addClass(Configuration.java:307)
	... 1 more
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for bars in class Foo
	at net.sf.hibernate.property.BasicPropertyAccessor.getGetter(BasicPropertyAccessor.java:186)
	at net.sf.hibernate.util.ReflectHelper.reflectedPropertyType(ReflectHelper.java:57)
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:91)
	... 8 more

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-440
    Summary: Direct collection property access 
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 5

   Assignee: Max Rydahl Andersen
   Reporter: Alexey Kaigorodov

    Created: Fri, 31 Oct 2003 3:26 AM
    Updated: Fri, 14 Nov 2003 5:23 PM

Description:
<bag name="..." access="field">
 ...
</bag>

causes exception unless exists getter

net.sf.hibernate.MappingException: Problem trying to set property type by reflection
	at net.sf.hibernate.mapping.Value.setTypeByReflection(Value.java:103)
	at net.sf.hibernate.cfg.Binder.createProperty(Binder.java:953)
	at net.sf.hibernate.cfg.Binder.propertiesFromXML(Binder.java:946)
	at net.sf.hibernate.cfg.Binder.bindRootClass(Binder.java:313)
	at net.sf.hibernate.cfg.Binder.bindRoot(Binder.java:1143)
	at net.sf.hibernate.cfg.Configuration.add(Configuration.java:243)
	at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:266)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:349)
	at net.sf.hibernate.cfg.Configuration.addJar(Configuration.java:320)
      ...
Caused by: net.sf.hibernate.PropertyNotFoundException: Could not find a getter for ... in class ...

--
With best regards,
Alexey


---------------------------------------------------------------------
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-476) Version is incorrect in Environment.java (should be "2.1 beta 6")

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Sun, 16 Nov 2003 8:06 PM

Yeah, we know about this one ... (my bad) .... its fixed in CVS (not that that helps much).
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-476
    Summary: Version is incorrect in Environment.java (should be "2.1 beta 6")
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 5

   Assignee: 
   Reporter: David D Phillips

    Created: Sun, 16 Nov 2003 6:11 PM
    Updated: Sun, 16 Nov 2003 8:06 PM

Description:
Version is incorrect in Environment.java - remember to change this for the final release!

It currently reads "2.1 beta 5", and should read "2.1 beta 6"


---------------------------------------------------------------------
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