Menu
▾
▴
hibernate-issues
|
From: <leg...@at...> - 2003-10-15 12:11:20
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Wed, 15 Oct 2003 7:10 AM
Body:
...to be able to just use the xml configuration file to setup the basic stuff....and then add mapping files via code...
We have the same possibility with hbm.xml files - they can also be totally empty ;)
---------------------------------------------------------------------
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: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Tue, 14 Oct 2003 12:24 AM
Updated: Wed, 15 Oct 2003 6:54 AM
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
|
|
From: <leg...@at...> - 2003-10-15 15:18:11
|
The following comment has been added to this issue:
Author: David Morris
Created: Wed, 15 Oct 2003 10:12 AM
Body:
In some cases I have configurations that only have dynamically configured mappings using Config.addClass(Class). I find this works very well and is more flexible. I haven't tested to confirm, but I suspect this reduces startup overhead for small standalone applications.
---------------------------------------------------------------------
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: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Tue, 14 Oct 2003 12:24 AM
Updated: Wed, 15 Oct 2003 6:54 AM
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
|
|
From: <leg...@at...> - 2004-03-08 21:15:19
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Mon, 8 Mar 2004 2:57 PM
Body:
eh - gavin, that did not make sense to me ;)
How can using hibernate.properties solve this one ?
The whole point were to use the xml based config instead of hibernate.properties and here it cannot be done because of (to me at least) non-logical limitation of the xml based config.
---------------------------------------------------------------------
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 2:57 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
|
|
From: <leg...@at...> - 2004-03-09 00:16:23
|
The following comment has been added to this issue:
Author: Gavin King
Created: Mon, 8 Mar 2004 5:58 PM
Body:
But there is exactly zero advantage to using XML instead of properties if there are no mapping files!
---------------------------------------------------------------------
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 5:58 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
|
|
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
|
|
From: <leg...@at...> - 2004-03-09 14:36:45
|
The following comment has been added to this issue:
Author: Christian Bauer
Created: Tue, 9 Mar 2004 8:18 AM
Body:
I'm +1 on just removing it. Had the same issue myself, don't want to use properties.
---------------------------------------------------------------------
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: Tue, 9 Mar 2004 8:18 AM
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
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X