[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2718?page=c...
]
Markus Maier commented on HHH-2718:
-----------------------------------
First, I hope cloning this issue was the right thing to do.
The problem I have is that the mapping DTD has changed in an* incompatible* way: the lazy
attribute for many-to-one can have the values (true|false|proxy) according to the
hibernate-mapping-3.0.dtd found in hibernate3.jar of the Hibernate 3.0.5 distribution,
while
http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd specifies
(false|proxy|no-proxy).
This results in XML editors (and the Hibernate Tools Eclipse plugin) using one kind of
definition while Hibernate itself uses another kind. I know that this will not be easy to
fix, but please at least try to avoid such mistakes in the future.
CLONE -Mapping DTD has changed from 3.0. A 3.1 version should be
released and made available
--------------------------------------------------------------------------------------------
Key: HHH-2718
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2718
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.1 beta 2
Environment: All
Reporter: Markus Maier
The Hibernate mapping DTD has changed in at least 1 detail, the lazy attribute of the
various Hibernate collections elements now supports {true, false, extra} rather than only
{true, false} as in 3.0.
I realize that you ship the DTD's in the Hibernate jars, so the differences are not
likely to effect the code, but XML editing tools will probably declare otherwise valid
documents invalid, since they are likely to access the DTD via the web rather than the
jar.
If the DTD references in the distributed hbm.xml files were modified then all of the
changes would be in sync.
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira