Hi,
On Thu, 23 Oct 2008 10:42:45 +0200, Adam Warski <[EMAIL PROTECTED]> wrote:
I can see the confusion. Hibernate has a similar annotation for
optimistic locking which nearly matches "Versioned" in Envers.
Yes, @Version. But it's for a totally different thing. So far I only
once I had a question on the forum if @Versioned and @Version are
related in any way. Do you really think it creates confusion?
I go with Steve here. I think 'Version' is really overloaded and there
will be
confusion between @Version and @Versioned, especially if they go into the
same code base.
Peronally, I consider the JPA @Version a bad name choice, but that cannot
be changed.
I also agree with Steve that auditing seems to be the right word. I was
several
times asked whether Hibernate supports auditing and when I asked what they
mean they
explained to me pretty much what Envers does.
If there would be a name change, then the old classes/annotations should
be deprecated, not removed - people wouldn't want to see their code
broken after upgrading to a newer version.
That depends on the already existing userbase. Just deprecating the
annotation might still
lead to confusion since it will be available at eg code completion. In my
opinion a clean start
would be nicer.
--Hardy
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
