[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