hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-291) support for select for update request for oracle on queries

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-291
    Summary: support for select for update request for oracle on queries
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: luc

    Created: Tue, 26 Aug 2003 2:38 AM
    Updated: Tue, 26 Aug 2003 2:38 AM

Description:
See the following post:





http://sourceforge.net/forum/forum.php?thread_id=922434&forum_id=128638


Thanks a lot


---------------------------------------------------------------------
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-289) using alias with id that isn't primary key causes where clauses to swap out to primary key name

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-289
    Summary: using alias with id that isn't primary key causes where clauses to swap out to primary key name
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 1

   Assignee: 
   Reporter: Mark Proctor

    Created: Mon, 25 Aug 2003 6:55 PM
    Updated: Mon, 25 Aug 2003 6:55 PM
Environment: Windows XP, Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

Description:
if I have  the following mapping file(note how I use "id" as name for a normal column, and guid as the primary key):
<hibernate-mapping>
    <class name="Revision" table="Revision">
    <id name="guid" type="java.lang.String" column="guid">
      <generator class="uuid.hex"/>
    </id>
    <property name="id" column="id" type="java.lang.String"/>
    <property name="version" column="version" type="long"/>
    <property name="fromDate" column="fromDate" type="java.util.Date"/>
    <property name="toDate" column="toDate" type="java.util.Date"/>
  </class>
</hibernate-mapping>

and I try the following query:
from com.domain.package.Revision as rev where rev.id=? and rev.toDate is null
I get id swapped out to guid, as shown in the SQL below:
select revision0_.guid as guid, revision0_.id as id, revision0_.version as version, revision0_.fromDate as fromDate, revision0_.toDate as toDate from Revision revision0_ where revision0_.guid=? )and(revision0_.toDate is null )

It works correctly  when aliases are not used, note how I have to use the table name directly on the where clauses, as you cant use the object name:
from com.domain.package.Revision where Revision.id=? and Revision.toDate is null

this gives the sql:
select revision0_.guid as guid, revision0_.id as id, revision0_.version as version, revision0_.fromDate as fromDate, revision0_.toDate as toDate from Revision revision0_ where (Revision.id=? )and(Revision.toDate is null )



---------------------------------------------------------------------
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-290) Allow component in IS NULL HQL

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-290
    Summary: Allow component in IS NULL HQL
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: Emmanuel Ligne

    Created: Tue, 26 Aug 2003 1:27 AM
    Updated: Tue, 26 Aug 2003 1:27 AM

Description:
Allow paths to components (or classes) in IS (not) NULL statement and
not only terminal properties. As long as component types are concerned,
testing "is null" corresponds to testing each column of the component
(or each column of the key for a class), based on the values returned
by the nullSafeSet(null) on the component or key type.

This would allow usage of multi-column ids, as for now these cannot
be used in HQL (cannot name each column as in composite-id).



---------------------------------------------------------------------
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] Problem with session.load() on hibernate 2.0

[Shamanth M. <sha...@ya...>]

When I do a session.load() on an object which has
complex many-many relationship with other objects I
get a strange kind of behaviour.
It happens to do a correct select first and then tries
to do an update and sometimes even delete.
This behaviour is seen only the first time I call
session.load().. Next time onwards it works perfectly
by doing only select quiries..

PLease help me in resolving the above issue..

1. How do I make hibernate not do a update or delete
when performing session.load().I tried playing around
with LOCKMOde with no suuccess.

2.If an update or delete is being done is it because
there's wroung data in the database? if so.. why
doesn't it get resolved once it does a update or
delete.. If I restart the server and access the same
record it again throws the same problem

I am getting the following exception when session.load
does an update or delete..
"exception setting property value with CGLIB setter of
"


Awaiting reply...
Thanks Shamanth Murthy



__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-288) Map.putAll() does not work

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

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Mon, 25 Aug 2003 2:31 PM

Yes, this embarrassing bug was already found and fixed in CVS.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-288
    Summary: Map.putAll() does not work
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Juha Komulainen

    Created: Mon, 25 Aug 2003 5:48 AM
    Updated: Mon, 25 Aug 2003 2:31 PM

Description:
net.sf.hibernate.collection.Map.putAll looks this:

    public void putAll(java.util.Map puts) {
        if ( map.size()>0 ) {
            write();
            map.putAll(puts);
        }
    }

The condition should clearly be "puts.size() > 0" instead
of "map.size() > 0".



---------------------------------------------------------------------
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-288) Map.putAll() does not work

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-288
    Summary: Map.putAll() does not work
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Juha Komulainen

    Created: Mon, 25 Aug 2003 5:48 AM
    Updated: Mon, 25 Aug 2003 5:48 AM

Description:
net.sf.hibernate.collection.Map.putAll looks this:

    public void putAll(java.util.Map puts) {
        if ( map.size()>0 ) {
            write();
            map.putAll(puts);
        }
    }

The condition should clearly be "puts.size() > 0" instead
of "map.size() > 0".



---------------------------------------------------------------------
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-287) documentation error - all-delete-orphan/s

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

Message:

   The following issue has been re-assigned.

   Assignee: Christian Bauer (mailto:chr...@hi...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Mon, 25 Aug 2003 12:35 AM
    Comment:
Christian, would you please fix the FAQ. I don't seem to have edit permissions on the Wiki yet.

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-287
    Summary: documentation error - all-delete-orphan/s
       Type: Improvement

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.0.2

   Assignee: Christian Bauer
   Reporter: Will Glass-Husain

    Created: Sun, 24 Aug 2003 2:20 AM
    Updated: Mon, 25 Aug 2003 12:35 AM

Description:
I think the below text should read "all-delete-orphan".  At least, that's what worked in Hibernate 2.0.2.  Using "all-delete-orphans" gave me an error (invalid cascade type).  Nice new feature, BTW.

Quoting: 
http://hibernate.bluemars.net/116.html

I removed an object from a collection mapped with cascade="all" but the object was not deleted!
cascade="all" cascades the delete() operation from parent to child. If this is a one-to-many association, try using cascade="all-delete-orphans".





---------------------------------------------------------------------
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-277) hbm2java generates wrong import with BinaryBlobType

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

The following issue has been updated:

    Updater: Thomas Jenny (mailto:t....@bl...)
       Date: Mon, 25 Aug 2003 1:21 AM
    Comment:
the generated source
    Changes:
             Attachment changed to AutoA.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-277
    Summary: hbm2java generates wrong import with BinaryBlobType 
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Thomas Jenny

    Created: Thu, 21 Aug 2003 4:31 AM
    Updated: Mon, 25 Aug 2003 1:21 AM
Environment: Hibernate 2.0.2, Hibernate extensions 2.0

Description:
in the mapping file, the following property is defined:

<property
    name="cryptedPassword"
    type="package.BinaryBlobType"
    column="CRYPTED_PASSWORD"
    length="4000"
    />

I'm using the class BinaryBlobType almost as defined at
http://hibernate.bluemars.net/73.html (imports adjusted to 
Hibernate 2)

hbm2java generates the following import:

import byte[];
...

When I remove the import, the code compiles and runs fine; 
but our automatic build cycle is currently broken because of 
this ...



---------------------------------------------------------------------
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-277) hbm2java generates wrong import with BinaryBlobType

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

The following issue has been updated:

    Updater: Thomas Jenny (mailto:t....@bl...)
       Date: Mon, 25 Aug 2003 1:20 AM
    Comment:
the mapping file
    Changes:
             Attachment changed to A.hbm.xml
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-277
    Summary: hbm2java generates wrong import with BinaryBlobType 
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Thomas Jenny

    Created: Thu, 21 Aug 2003 4:31 AM
    Updated: Mon, 25 Aug 2003 1:20 AM
Environment: Hibernate 2.0.2, Hibernate extensions 2.0

Description:
in the mapping file, the following property is defined:

<property
    name="cryptedPassword"
    type="package.BinaryBlobType"
    column="CRYPTED_PASSWORD"
    length="4000"
    />

I'm using the class BinaryBlobType almost as defined at
http://hibernate.bluemars.net/73.html (imports adjusted to 
Hibernate 2)

hbm2java generates the following import:

import byte[];
...

When I remove the import, the code compiles and runs fine; 
but our automatic build cycle is currently broken because of 
this ...



---------------------------------------------------------------------
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-277) hbm2java generates wrong import with BinaryBlobType

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

The following issue has been updated:

    Updater: Thomas Jenny (mailto:t....@bl...)
       Date: Mon, 25 Aug 2003 1:20 AM
    Comment:
The binary blob type
    Changes:
             Attachment changed to BinaryBlobType.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-277
    Summary: hbm2java generates wrong import with BinaryBlobType 
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Max Rydahl Andersen
   Reporter: Thomas Jenny

    Created: Thu, 21 Aug 2003 4:31 AM
    Updated: Mon, 25 Aug 2003 1:20 AM
Environment: Hibernate 2.0.2, Hibernate extensions 2.0

Description:
in the mapping file, the following property is defined:

<property
    name="cryptedPassword"
    type="package.BinaryBlobType"
    column="CRYPTED_PASSWORD"
    length="4000"
    />

I'm using the class BinaryBlobType almost as defined at
http://hibernate.bluemars.net/73.html (imports adjusted to 
Hibernate 2)

hbm2java generates the following import:

import byte[];
...

When I remove the import, the code compiles and runs fine; 
but our automatic build cycle is currently broken because of 
this ...



---------------------------------------------------------------------
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-287) documentation error - all-delete-orphan/s

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-287
    Summary: documentation error - all-delete-orphan/s
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.0.2

   Assignee: 
   Reporter: Will Glass-Husain

    Created: Sun, 24 Aug 2003 2:20 AM
    Updated: Sun, 24 Aug 2003 2:20 AM

Description:
I think the below text should read "all-delete-orphan".  At least, that's what worked in Hibernate 2.0.2.  Using "all-delete-orphans" gave me an error (invalid cascade type).  Nice new feature, BTW.

Quoting: 
http://hibernate.bluemars.net/116.html

I removed an object from a collection mapped with cascade="all" but the object was not deleted!
cascade="all" cascades the delete() operation from parent to child. If this is a one-to-many association, try using cascade="all-delete-orphans".





---------------------------------------------------------------------
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-274) bin scripts addition / rewrite

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

Message:

   The following issue has been re-assigned.

   Assignee: Christian Bauer (mailto:chr...@hi...)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-274
    Summary: bin scripts addition / rewrite
       Type: Improvement

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
             toolset
   Versions:
             2.0rc2
             2.1
             2.0 final
             2.0.1
             2.0.2
             2.0.3
             2.1 beta 1
             2.1 beta 2

   Assignee: Christian Bauer
   Reporter: Les Hazlewood

    Created: Tue, 19 Aug 2003 7:38 AM
    Updated: Sat, 23 Aug 2003 6:31 AM
Environment: windows (all), *nix

Description:
I downloaded the latest beta binary version of Hibernate this morning and untarred it to start using it.  However, I noticed there were no linux binary scripts to run.  So I created some :)  I also re-wrote the windows batch scripts to be more robust and flexible with respect to how classpaths are set. 

I didn't test the windows scripts, so someone needs to run them on a windows box to make sure they work (although the code is pretty trivial and should run nicely).  The linux scripts all work properly (I tested all of them) and are chmodded to execute permissions.  If you manipulate these files in an ant build (or copy them from one location to another during build time), please ensure that the <chmod/> ant task sets the execute permissions properly for *nix users. 

The directory structure of the file I have is as follows: 

bin-scripts
 |
 |--bin (rewritten and new Hibernate bin scripts, for win and *nix)
 |
 |--tools
     |
     |--bin (rewritten and new Tools bin scripts, for win and *nix). 

Naturally, please feel free to format/rewrite/reuse the code however you feel that it may benefit Hibernate.

Apparently, this "create new issue" page does not allow file uploads, so please email pha...@us... to let me know to whom I may send the tarball.


---------------------------------------------------------------------
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-50) Reference Documentation translation to pt-BR

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

Message:

   The following issue has been re-assigned.

   Assignee: Christian Bauer (mailto:chr...@hi...)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-50
    Summary: Reference Documentation translation to pt-BR
       Type: Patch

     Status: Assigned
   Priority: Major

    Project: Hibernate2

   Assignee: Christian Bauer
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:32 AM
    Updated: Sat, 23 Aug 2003 6:31 AM

Description:
Reference Documentation translation to pt-BR
A pt-BR translation of Refernce Documentation 

Inside the patch are 1 file and 1 directory. 

The file is a patch that add 3 targets that generate the 
3 kind of documentations 
The directory pt_br must be placed in: 
doc/reference/src 

http://sourceforge.net/tracker/index.php?func=detail&aid=724825&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-283) Parent class constructor error - prevents compilation of a project

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

The following comment has been added to this issue:

     Author: Les Hazlewood
    Created: Sat, 23 Aug 2003 12:02 PM
       Body:
You da man Max!

Thanks very very much!

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-283
    Summary: Parent class constructor error - prevents compilation of a project
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Fri, 22 Aug 2003 9:38 AM
    Updated: Fri, 22 Aug 2003 5:14 PM
Environment: all

Description:
A rewrite of the email I wrote after discovering this bug:

I think I've discovered a fairly serious bug with the joined-subclass class generation.  Max Anderson confirmed this sounds like a bug, so I'm adding it to JIRA.

(Please open attached hbm.xml file for reference when reading the rest of this description):

Given the schema, 

a User ISA Person ISA Party ISA DatabaseObject. 

However, the generated code for the User class calls (in its "minimal" 
constructor): 

super(dbCreationTs, emailAddresses, phoneNumbers, postalAddresses, name); 

There is no constructor in the Person class with that signature (however, there is one like that in the Party class, which is the "Grandparent" of User.  The Person class has only one constructor (no minimal constructor), and its signature is: 

Person (Calendar dbCreationTs, Set emailAddresses, Set phoneNumbers,  Set postalAddresses, String gender, PersonName name); 

Therefore, the User class, in its minimal constructor, is trying to call a super constructor that doesn't exist (its actually trying to call a Grandparent constructor). 

I manually typed in a minimal constructor for Person just like the full constructor above, but leaving out gender, since it is nullable. (I believe this is how you generate a "minimal" constructor - leaving out nullable fields - but I could be wrong).  After doing that, everything compiled fine.

Is there a way that an update could be written fairly soon?  Generated class compilation errors is a pretty substantial bug that would affect anyone.  I also can't continue my current project until the correct OO hierarchy is in place and compiles.  I am certainly willing to help out in any way that I can (testing, coding, etc).

Thanks! 

Les Hazlewood 


---------------------------------------------------------------------
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-229) Joined-subclass definitions in separate .hbm.xml

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

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Sat, 23 Aug 2003 3:18 PM

Feels good to nail this OLD feature request ;)
This is now fixed v21branch in CVS.

<subclass> and <joined-subclass> can now have an extends attribute that contains the fully qualified classname of its superclass.

NOTE: the superclass HAS TO BE defined BEFORE it is reference from extends. This means ordering of the hbm.xml files is now relevant!


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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-229
    Summary: Joined-subclass definitions in separate .hbm.xml
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: FIXED

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

   Assignee: 
   Reporter: Duffy Gillman

    Created: Mon, 4 Aug 2003 6:40 PM
    Updated: Sat, 23 Aug 2003 3:18 PM
Environment: All

Description:
Currently all joined-subclass definitions must be contained in the hbm.xml file that defines the superclass.  In application frameworks built on top of Hibernate, this could be very limiting.  In order to allow someone to extend key framework classes, that person must currently edit the configuration files of the framework classes.  It would be very useful to allow new subclasses to be defined in external hbm files.

A new "superclass" attribute could be created for the class element, along with a "inheritanceType=joined|determinant".  When a new hbm file is processed by a DataStore the superclass attribute could be examined and the new class could be treated as a subclass or joined-subclass based on the inheritanceType attribute.  This would place a constraint on the order in which resources are added to the DataStore.  The superclass will need to be added first, or there will have to be a check for completeness of mapping definitions at the point when a SessionFactory is created.


---------------------------------------------------------------------
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-280) support formula properties in where clause

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

Message:

   The following issue has been re-assigned.

   Assignee: Gavin King (mailto:ga...@in...)
   Assigner: Max Rydahl Andersen (mailto:xa...@xa...)
       Date: Sat, 23 Aug 2003 7:22 PM
    Comment:
back at ya' ;)

I've concluded that it is doable, but it seem to require a refactoring of the formula code so it is datastructures are accessible from AbstractEntityPersister instead of just in EntityPersister.

I'll let you stear (or sharpen) the knife on this one ;)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-280
    Summary: support formula properties in where clause
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: Gavin King
   Reporter: Tim Schafer

    Created: Thu, 21 Aug 2003 6:23 PM
    Updated: Sat, 23 Aug 2003 7:22 PM

Description:
Be able to use the property in an HQL where clause
and have the formula inserted into the resulting SQL


---------------------------------------------------------------------
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-286) Support for discriminator when using <joined-subclass>

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-286
    Summary: Support for discriminator when using <joined-subclass>
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: Kenneth Foo

    Created: Sat, 23 Aug 2003 9:35 PM
    Updated: Sat, 23 Aug 2003 9:35 PM
Environment: Windows XP Pro, JDK 1.4.2, Hibernate 2.0.2, HSQLDB 1.7.1

Description:

Descriminators are only available when using <subclass>, but
not currently supported when using <joined-subclass>.

For performance reasons, would be great if <joined-subclass> supported this too.

Assume the following class hierarchy

class A;
class B extends A;
class C extends A;
class D extends A;
class E extends A;

An ID named "id" is defined in A.
In my object model, there are MANY classes which derive from A.
We map them as table-per-class using <joined-subclass>.

When <joined-subclass> is used (due to database limitation, I HAVE to use this), Hibernate issues a query which involves multiple joins across the table. This is inefficient as it might involve multiple table locks/index scans on some databases. It is made even worse when we have an object model where there are many derivatives of A.

I propose that discriminators are allowed in such a condition such that the unnecessary joins and lookups are avoided.



---------------------------------------------------------------------
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-283) Parent class constructor error - prevents compilation of a project

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

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Fri, 22 Aug 2003 5:14 PM

back - try now ;)


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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-283
    Summary: Parent class constructor error - prevents compilation of a project
       Type: Bug

     Status: Closed
   Priority: Critical
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Fri, 22 Aug 2003 9:38 AM
    Updated: Fri, 22 Aug 2003 5:14 PM
Environment: all

Description:
A rewrite of the email I wrote after discovering this bug:

I think I've discovered a fairly serious bug with the joined-subclass class generation.  Max Anderson confirmed this sounds like a bug, so I'm adding it to JIRA.

(Please open attached hbm.xml file for reference when reading the rest of this description):

Given the schema, 

a User ISA Person ISA Party ISA DatabaseObject. 

However, the generated code for the User class calls (in its "minimal" 
constructor): 

super(dbCreationTs, emailAddresses, phoneNumbers, postalAddresses, name); 

There is no constructor in the Person class with that signature (however, there is one like that in the Party class, which is the "Grandparent" of User.  The Person class has only one constructor (no minimal constructor), and its signature is: 

Person (Calendar dbCreationTs, Set emailAddresses, Set phoneNumbers,  Set postalAddresses, String gender, PersonName name); 

Therefore, the User class, in its minimal constructor, is trying to call a super constructor that doesn't exist (its actually trying to call a Grandparent constructor). 

I manually typed in a minimal constructor for Person just like the full constructor above, but leaving out gender, since it is nullable. (I believe this is how you generate a "minimal" constructor - leaving out nullable fields - but I could be wrong).  After doing that, everything compiled fine.

Is there a way that an update could be written fairly soon?  Generated class compilation errors is a pretty substantial bug that would affect anyone.  I also can't continue my current project until the correct OO hierarchy is in place and compiles.  I am certainly willing to help out in any way that I can (testing, coding, etc).

Thanks! 

Les Hazlewood 


---------------------------------------------------------------------
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] Reopened: (HB-283) Parent class constructor error - prevents compilation of a project

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

Message:

   The following issue has been reopened.

   Reopener: Max Rydahl Andersen
       Date: Fri, 22 Aug 2003 5:12 PM

sorry - that introduced a new bug....will be back shortly with a fix....
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-283
    Summary: Parent class constructor error - prevents compilation of a project
       Type: Bug

     Status: Reopened
   Priority: Critical

    Project: Hibernate2
 Components: 
             core

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Fri, 22 Aug 2003 9:38 AM
    Updated: Fri, 22 Aug 2003 5:12 PM
Environment: all

Description:
A rewrite of the email I wrote after discovering this bug:

I think I've discovered a fairly serious bug with the joined-subclass class generation.  Max Anderson confirmed this sounds like a bug, so I'm adding it to JIRA.

(Please open attached hbm.xml file for reference when reading the rest of this description):

Given the schema, 

a User ISA Person ISA Party ISA DatabaseObject. 

However, the generated code for the User class calls (in its "minimal" 
constructor): 

super(dbCreationTs, emailAddresses, phoneNumbers, postalAddresses, name); 

There is no constructor in the Person class with that signature (however, there is one like that in the Party class, which is the "Grandparent" of User.  The Person class has only one constructor (no minimal constructor), and its signature is: 

Person (Calendar dbCreationTs, Set emailAddresses, Set phoneNumbers,  Set postalAddresses, String gender, PersonName name); 

Therefore, the User class, in its minimal constructor, is trying to call a super constructor that doesn't exist (its actually trying to call a Grandparent constructor). 

I manually typed in a minimal constructor for Person just like the full constructor above, but leaving out gender, since it is nullable. (I believe this is how you generate a "minimal" constructor - leaving out nullable fields - but I could be wrong).  After doing that, everything compiled fine.

Is there a way that an update could be written fairly soon?  Generated class compilation errors is a pretty substantial bug that would affect anyone.  I also can't continue my current project until the correct OO hierarchy is in place and compiles.  I am certainly willing to help out in any way that I can (testing, coding, etc).

Thanks! 

Les Hazlewood 


---------------------------------------------------------------------
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] Resolved: (HB-283) Parent class constructor error - prevents compilation of a project

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

Message:

   The following issue has been resolved as FIXED.

   Resolver: Max Rydahl Andersen
       Date: Fri, 22 Aug 2003 3:59 PM

i think i've fixed it in the CVS now.

Was a simple mistake in the code that decided if a minimal constructor was needed that only would fail in hiearchies larger than 2 - thanks for finding that one ;)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-283
    Summary: Parent class constructor error - prevents compilation of a project
       Type: Bug

     Status: Resolved
   Priority: Critical
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Fri, 22 Aug 2003 9:38 AM
    Updated: Fri, 22 Aug 2003 3:59 PM
Environment: all

Description:
A rewrite of the email I wrote after discovering this bug:

I think I've discovered a fairly serious bug with the joined-subclass class generation.  Max Anderson confirmed this sounds like a bug, so I'm adding it to JIRA.

(Please open attached hbm.xml file for reference when reading the rest of this description):

Given the schema, 

a User ISA Person ISA Party ISA DatabaseObject. 

However, the generated code for the User class calls (in its "minimal" 
constructor): 

super(dbCreationTs, emailAddresses, phoneNumbers, postalAddresses, name); 

There is no constructor in the Person class with that signature (however, there is one like that in the Party class, which is the "Grandparent" of User.  The Person class has only one constructor (no minimal constructor), and its signature is: 

Person (Calendar dbCreationTs, Set emailAddresses, Set phoneNumbers,  Set postalAddresses, String gender, PersonName name); 

Therefore, the User class, in its minimal constructor, is trying to call a super constructor that doesn't exist (its actually trying to call a Grandparent constructor). 

I manually typed in a minimal constructor for Person just like the full constructor above, but leaving out gender, since it is nullable. (I believe this is how you generate a "minimal" constructor - leaving out nullable fields - but I could be wrong).  After doing that, everything compiled fine.

Is there a way that an update could be written fairly soon?  Generated class compilation errors is a pretty substantial bug that would affect anyone.  I also can't continue my current project until the correct OO hierarchy is in place and compiles.  I am certainly willing to help out in any way that I can (testing, coding, etc).

Thanks! 

Les Hazlewood 


---------------------------------------------------------------------
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-283) Parent class constructor error - prevents compilation of a project

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Fri, 22 Aug 2003 3:37 PM
       Body:
I see it ;)

Two things:

1. I i'm really really considering to drop all that full/minimal constructor stuff! It is reaaaaallly messy ;) (that would solve your problem i reckon)

2. I'll suggest you look at the RootPersistent Class design pattern in the wiki - it is not necessary a Good Thing to make all your mappings descend from the same mapped root class....just a suggestion.


...and i'm looking into this now - i'll see what i can do about 1.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-283
    Summary: Parent class constructor error - prevents compilation of a project
       Type: Bug

     Status: In Progress
   Priority: Critical

    Project: Hibernate2
 Components: 
             core

   Assignee: Max Rydahl Andersen
   Reporter: Les Hazlewood

    Created: Fri, 22 Aug 2003 9:38 AM
    Updated: Fri, 22 Aug 2003 3:34 PM
Environment: all

Description:
A rewrite of the email I wrote after discovering this bug:

I think I've discovered a fairly serious bug with the joined-subclass class generation.  Max Anderson confirmed this sounds like a bug, so I'm adding it to JIRA.

(Please open attached hbm.xml file for reference when reading the rest of this description):

Given the schema, 

a User ISA Person ISA Party ISA DatabaseObject. 

However, the generated code for the User class calls (in its "minimal" 
constructor): 

super(dbCreationTs, emailAddresses, phoneNumbers, postalAddresses, name); 

There is no constructor in the Person class with that signature (however, there is one like that in the Party class, which is the "Grandparent" of User.  The Person class has only one constructor (no minimal constructor), and its signature is: 

Person (Calendar dbCreationTs, Set emailAddresses, Set phoneNumbers,  Set postalAddresses, String gender, PersonName name); 

Therefore, the User class, in its minimal constructor, is trying to call a super constructor that doesn't exist (its actually trying to call a Grandparent constructor). 

I manually typed in a minimal constructor for Person just like the full constructor above, but leaving out gender, since it is nullable. (I believe this is how you generate a "minimal" constructor - leaving out nullable fields - but I could be wrong).  After doing that, everything compiled fine.

Is there a way that an update could be written fairly soon?  Generated class compilation errors is a pretty substantial bug that would affect anyone.  I also can't continue my current project until the correct OO hierarchy is in place and compiles.  I am certainly willing to help out in any way that I can (testing, coding, etc).

Thanks! 

Les Hazlewood 


---------------------------------------------------------------------
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-275) hbm2java generates broken property change code

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

Message:

   The following issue has been closed.

   Resolver: Max Rydahl Andersen
       Date: Fri, 22 Aug 2003 4:59 AM

is fixed in CVS
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-275
    Summary: hbm2java generates broken property change code
       Type: Patch

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             toolset
   Fix Fors:
             2.1
   Versions:
             2.0 final

   Assignee: Max Rydahl Andersen
   Reporter: Shane Day

    Created: Wed, 20 Aug 2003 4:07 AM
    Updated: Fri, 22 Aug 2003 4:59 AM
Environment: OS X, Hibernate 2.0.2, extensions 2.0

Description:
The generated setter methods call changeSupport.firePropertyChange with the old value being the same as the new. The first thing firePropertyChange does is return if there is no change in the value.

The getFieldAsObject method of BasicRenderer fails to prepend "this." for non-primitive types.

The following patch fixes getFieldAsObject and adds generated code that backs up the old value before setting it, and parses this old value to firePropertyChange. It may be ok to call firePropertyChange before updating the member, thus avoiding the oldValue variable, but it feels better to send the event after making the change.

Sorry about the tab/space conversion in the patch. My editor auto-converts to spaces.

Cheers
  Shane Day


*** /Users/shane/opt/hibernate-extensions-2.0.bak/tools/src/net/sf/hibernate/tool/hbm2java/BasicRenderer.java	Sat Jun 14 00:15:31 2003
--- BasicRenderer.java	Wed Aug 20 19:58:04 2003
***************
*** 393,402 ****
              		writer.println("                "+getFieldAsObject(true, field)+",");
              		writer.println("                "+getFieldAsObject(false, field)+");");
  			}
              writer.println("        this." + field.getName() + " = " + field.getName() + ";");
              if((fieldType&BOUND)==BOUND) {
              		writer.println("        "+changeSupport+".firePropertyChange(\""+field.getName()+"\",");
!             		writer.println("                "+getFieldAsObject(true, field)+",");
              		writer.println("                "+getFieldAsObject(false, field)+");");
              }
              writer.println("    }");
--- 393,406 ----
                          writer.println("                "+getFieldAsObject(true, field)+",");
                          writer.println("                "+getFieldAsObject(false, field)+");");
                          }
+ 
+             if((fieldType&BOUND)==BOUND) {
+               writer.println("        Object oldValue = "+getFieldAsObject(true, field));
+             }
              writer.println("        this." + field.getName() + " = " + field.getName() + ";");
              if((fieldType&BOUND)==BOUND) {
                          writer.println("        "+changeSupport+".firePropertyChange(\""+field.getName()+"\",");
!                         writer.println("                oldValue,");
                          writer.println("                "+getFieldAsObject(false, field)+");");
              }
              writer.println("    }");
***************
*** 477,483 ****
  						typeName += prependThis ? "this." : "";
  						return typeName+field.getName()+" )";        			
  				}
! 				return field.getName();
  		}
  
  }
--- 481,487 ----
                                                  typeName += prependThis ? "this." : "";
                                                  return typeName+field.getName()+" )";
                                  }
!                                 return (prependThis?"this.":"")+field.getName();
                  }
  
  }



---------------------------------------------------------------------
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-140) Changed Avalon component to work with cocoon 2.0.4

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

The following comment has been added to this issue:

     Author: Eric Pugh
    Created: Fri, 22 Aug 2003 3:20 PM
       Body:
apparently there is some confusion on this bug.  Whether the interface HibernateService should extend Component or not..

I am going to write Neeme and the Avalon team and see what's up..  I always though you did need to extend a "work" interface.
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-140
    Summary: Changed Avalon component to work with cocoon 2.0.4
       Type: Patch

     Status: Assigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             toolset

   Assignee: Eric Pugh
   Reporter: Scott Payne

    Created: Wed, 18 Jun 2003 12:47 AM
    Updated: Fri, 20 Jun 2003 11:58 PM

Description:
Simple patch so that the CocoonComponentManager won't throw a ClassCastException when using the HibernateService. It seemed to try to cast it to a Component (fair enough) and this fixed it.

Also a change to the DTD used in the test case, to use the hibernate 2 DTD.


diff -riuwBb -x CVS avalon/src/java/net/sf/hibernate/avalon/HibernateService.java avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java
--- avalon/src/java/net/sf/hibernate/avalon/HibernateService.java	2003-06-18 15:37:40.000000000 +1000
+++ avalon-patched/src/java/net/sf/hibernate/avalon/HibernateService.java	2003-06-18 15:21:00.000000000 +1000
@@ -11,7 +11,7 @@
  * @author <a href="mailto:ne...@ap...">Neeme Praks</a>
  * @version $Id: HibernateService.java,v 1.2 2003/06/04 10:44:25 nemecec Exp $
  */
-public interface HibernateService {
+public interface HibernateService extends org.apache.avalon.framework.component.Component {
 
     public static final String ROLE = HibernateService.class.getName();


diff -riuwBb -x CVS avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml
--- avalon/src/test/net/sf/hibernate/avalon/Labor.hbm.xml	2003-06-18 15:37:50.000000000 +1000
+++ avalon-patched/src/test/net/sf/hibernate/avalon/Labor.hbm.xml	2003-06-18 15:25:31.000000000 +1000
@@ -1,7 +1,7 @@
 <?xml version="1.0"?>
   <!DOCTYPE hibernate-mapping PUBLIC
-     "-//Hibernate/Hibernate Mapping DTD//EN"
-     "http://hibernate.sourceforge.net/hibernate-mapping.dtd">
+    "-//Hibernate/Hibernate Mapping DTD 2.0//EN" 
+    "http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
 
   <hibernate-mapping>
     <class name="net.sf.hibernate.avalon.Labor" table="LABOR" >




---------------------------------------------------------------------
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-285) EXPRESSIONS AND CONSTANTS SUPPORT FOR HQL

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-285


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-285
    Summary: EXPRESSIONS AND CONSTANTS SUPPORT FOR HQL
       Type: New Feature

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components:=20
             core
   Versions:
             2.1 beta 2

   Assignee:=20
   Reporter: Jes=C3=BAs Ramos Cardona

    Created: Fri, 22 Aug 2003 2:25 PM
    Updated: Fri, 22 Aug 2003 2:25 PM
Environment: J2EE Application deployed on WebLogic 8.1.0, running on Solari=
s 8. Hibernate Persistant Objects used inside Session EJBs.

Description:
Support for CONSTANTS and EXPRESSIONS for Hibernate Query Language would ve=
ry much come in handy. Specially when facing the need to execute statements=
 like:

SELECT new com.vault.model.[JavaBean](branch.id, branch.status, branch.name=
1, [:variable|expression|constant])
FROM Branch as branch
WHERE branch.id =3D :id

KEY:
*[JavaBean] - self-explainatory.
*[:variable|expression|constant] - Instead of an object.member, one would b=
e able to include expressions or variables (ie :myVar).

Would OGNL (or a tweak of the same) be the choice for appropiate expression=
 support?


---------------------------------------------------------------------
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-280) support formula properties in where clause

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

Message:

   The following issue has been re-assigned.

   Assignee: Max Rydahl Andersen (mailto:xa...@xa...)
   Assigner: Gavin King (mailto:ga...@in...)
       Date: Fri, 22 Aug 2003 1:29 PM
    Comment:
Assign back to me if it gets too hairy ;)
---------------------------------------------------------------------
View the issue:

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-280
    Summary: support formula properties in where clause
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core

   Assignee: Max Rydahl Andersen
   Reporter: Tim Schafer

    Created: Thu, 21 Aug 2003 6:23 PM
    Updated: Fri, 22 Aug 2003 1:29 PM

Description:
Be able to use the property in an HQL where clause
and have the formula inserted into the resulting SQL


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