[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-3439) Change o.h.cfg.Mappings to not require constructor

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-3439.
-------------------------------

    Resolution: Fixed

For the time being, I just did the simpliest here to insulate us from any further additions in 3.4.  Lets re-visit for 4.0

> Change o.h.cfg.Mappings to not require constructor
> --------------------------------------------------
>
>                 Key: HHH-3439
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3439
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: metamodel
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 3.4
>
>
> Mappings requiring passing all the mapping queues into its constructor causes interoperability issues with other components (annotations e.g.) because they generally extend Mappings to add extra information.  Therefore we introduce an incompatibility whenever we add a new mapping attribute because we are currently forced to change the signature of the Mappings constructor.
> A better approach is to make Mappings an interface with an impl that defined as an inner class to o.h.cfg.Configuration so that it can expose access to the queues directly from there.  Annotations, etc can than simply extend that Mappings impl. 

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira