Well, I imported the Hibernate2 sourcetree last night. Its in
its own module which means that for the next couple of months
we need to be *very* careful about handling patches. Bugfixes
and minor improvements must be applied against *both* trees.
(New features need only go into the Hibernate2 module.) As
promised, the following changes were made:
* packages are now net.sf.hibernate.*
* project structure is changed; all java is now in src dir
* code and tests relating to toplevel collections and=20
subcollections was removed
I have created a new hibernate-mapping-2.0.dtd, since we no
longer need the <collection>, <subcollection>, <generated-key>
elements and since collections may no longer appear beneath
the root element.
In the new DTD, I have also renamed the 'readonly' attribute=20
to 'inverse', since its name was causing all kinds of confusion=20
for new (and not-so-new) users.
Please vote on the following proposals:
* Rename the 'role' attribute to 'name' in all collection
elements in the new DTD, for consistency with <many-to-one>,=20
<id> and <property> elements. The role attribute no longer
has any extra semantics beyond being a simple property
name.
I am +1
* Change the default for unsaved-value to "null" in the new=20
DTD. The current default is surprising to new users.
I am +1
* Change the default for default-cascade to "save-update"
in the new DTD.
I am undecided ... interested to hear the views of others.
* Remove the exception that occurs if you save an object
that is already associated with the session. This
makes save() consistent with saveOrUpdate().
I am probably a +1 on this
* Remove the exception that occurs if you delete an object
that is already deleted in that session.=20
I am undecided. The current behaviour forces people to
think about who "owns" an object, who is responsible for
deleting it. However, it *can* be a pain in the ass.
In particular it means that:
session.delete("from o in class java.lang.Object");
never has any possibility of success if you use cascade
delete anywhere.
None of the above proposals would break existing code that
uses the old mapping DTDs. The actual changes to default
values can be made just in the DTD.
Gavin.
********** CAUTION - Disclaimer **********
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS******** End of Disclaimer **********
|
