[hibernate-dev] Re: Hibernate Search: approval for changes, "commit conventions"?
Max Bowsher
maxb at f2s.com
Fri May 30 06:49:41 EDT 2008
Sanne Grinovero wrote:
> I knew about the requirement to change the UID, but really hadn't a
> clue about the default behaviour:
> I thought it was "unspecified" and I really dislike that word.
The default behaviour is semi-specified - specifically, it's based on a
SHA1 hash of:
class name and modifiers
implemented interface names
field names, types and modifiers
(excluding 'private static' and 'private transient' fields)
presence of a static initializer
constructor signatures and modifiers
(excluding private constructors)
method names, signatures and modifiers
(excluding private methods)
The "unspecified" bit creeps in because it's not specified precisely
what synthetic members and classes used to implement language features
like class literals and inner classes should be named, so different
compiler implementations are free to make different choices, giving
different generated UIDs.
Max.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/hibernate-dev/attachments/20080530/73292058/attachment.bin
More information about the hibernate-dev
mailing list