I'm really in-between on this naming actually. I think 'historize' is the correct term for what envers does. But since 'historize' is not a real dictionary word I am nervous to use it in the actual annotation (though google shows that it is indeed a well used/understood computer engineering term).
I'd say either @Audited or @Historized. @Audited sounds more "natural" to me, but like I said above I think @Historized is more "correct". - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] Principal Software Engineer JBoss, a division of Red Hat http://jboss.com http://redhat.com [EMAIL PROTECTED] [EMAIL PROTECTED] On Thu, 2008-10-23 at 10:16 -0400, Emmanuel Bernard wrote: > > On Oct 23, 2008, at 07:18, Adam Warski 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. > > Ok then :). @Historized? @Historic? > > @Audited > @Archived > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
