|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-05-09 22:44:49
|
[ http://216.121.112.228/browse/NH-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-1921.
---------------------------
Resolution: Won't Fix
Problem solved by mapping-by-code.
> Possibility to improve hbm.xml Mapping file configuration
> ---------------------------------------------------------
>
> Key: NH-1921
> URL: http://216.121.112.228/browse/NH-1921
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.1.GA
> Reporter: BNReddy
> Priority: Minor
> Attachments: Child.xml, Parent.hbm.xml
>
>
> My project is having a lot of hbm.xml files in which most of the hbm.xml files are having same component configuration.
> Problem is if add/remove a member which should be reflected under database leads to update all hbm.xml files where it is configured.
> I can make it as a separate entity and I can proceed. Other than this solution, is there any other solution.
> If not, why can't NH allow to use <xi:include href="filename"/> concept. Providing separate xml file for component and ref the xml file where it is required.
> Future changes requires to change only one xml file which will reduce all refered xml files update.
> Please find the attached sample xml files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|