From: <leg...@at...> - 2004-03-09 05:11:31
|
The following comment has been added to this issue: Author: David Morris Created: Mon, 8 Mar 2004 10:52 PM Body: I submitted this because I thought it was a bug since mappings can be configured outside of the xml config and Hibernate works just fine with dynamically loaded mappings. I did this to minimize the startup time for applications that use a small subset of defined mappings. My current workaround is to use a modified internal DTD, which is a minor inconvenience that is worth it considering the performance gain. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-397 Summary: Hibernate configuration DTD should not require mapping(s) Type: Improvement Status: Closed Priority: Minor Resolution: REJECTED Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: David Morris Created: Tue, 14 Oct 2003 12:24 AM Updated: Mon, 8 Mar 2004 10:52 PM Description: The hibernate-configuration dtd defines mapping as a 1-many relationship to mappings. This makes it impossible to use a session configuration without at least one mapping defined. I have attached a patch, however the change is trivial, just change mapping+ to mapping* in http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd (will this become 2.1?). --------------------------------------------------------------------- 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 |