[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-229) Joined-subclass definitions in separate .hbm.xml

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

The following issue has been updated:

    Updater: Max Rydahl Andersen (mailto:xa...@xa...)
       Date: Fri, 22 Aug 2003 5:17 AM
    Comment:
same patch - just extended with a "secondpass class resolver" for classes that is defined before their superclass is defined.

Also added inheritance cyclic check - just in case i've missed any validity checks ;)


    Changes:
             Attachment changed to noorderingextends.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

---------------------------------------------------------------------
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: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 1

   Assignee: 
   Reporter: Duffy Gillman

    Created: Mon, 4 Aug 2003 6:40 PM
    Updated: Fri, 22 Aug 2003 5:17 AM
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