After the latest changes all locks between different DirectoryProviders
are gone and "sequentiality" is no longer needed, I would like to
have the changes made on different DP happen concurrently,
this is needed for several other optimizations.
the workQueue gets split by DP (code exists already),
The idea, moving forward, is to start pushing the Annotations approach
more than we do now. Not to deprecate xml mappings per-se but certainly
to start looking at Annotations as the preferred approach. At that
point we'd stop developing the HbmBinder code (aside from bug fixes).
Note that this is
Yes I think it will really lead to confusion.
Deprecation seems reasonable. So lets get this migrated for Hibernate's
3.4/3.5 release with the deprecations noting removal in 4.0.
-
Steve Ebersole
Project Lead
http://hibernate.org
[EMAIL PROTECTED]
Principal Software Engineer
JBoss, a divisio
You can still target just Annotation/EntityManager environments if you
want. Nothing in this move precludes that because Annotations and
EntityManager themselves will be doing similar moves.
-
Steve Ebersole
Project Lead
http://hibernate.org
[EMAIL PROTECTED]
Principal Software Engineer
JBoss
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
This is exactly what we discussed yesterday on IRC.
-
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 Wed, 2008-10-22 at 19:48 -0400, Emmanuel
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
Adam Warski wrote:
> Hello,
>
>>> Though I'd have to do some adaptation changes. As I was originally
>>> targeting Envers to support JPA mappings, I assumed that it will be
>>> working in an enviroment with Hibernate Annotations/EntityManager. So
>>> I used ReflectionManager to read the @Versioned
Hello,
Though I'd have to do some adaptation changes. As I was originally
targeting Envers to support JPA mappings, I assumed that it will be
working in an enviroment with Hibernate Annotations/EntityManager.
So I used ReflectionManager to read the @Versioned annotations. In
a pure Hibern
Hello,
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
Hi,
On Thu, 23 Oct 2008 12:17:18 +0200, Adam Warski <[EMAIL PROTECTED]> wrote:
Though I'd have to do some adaptation changes. As I was originally
targeting Envers to support JPA mappings, I assumed that it will be
working in an enviroment with Hibernate Annotations/EntityManager. So I
used
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 reall
Hello,
I wonder if it really has to be a project on its own?
A module in core would make more sense?
I wouldn't have anything against :)
Though I'd have to do some adaptation changes. As I was originally
targeting Envers to support JPA mappings, I assumed that it will be
working in an envi
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 quest
On Wed, 22 Oct 2008 17:11:01 +0200, Juraci Costa <[EMAIL PROTECTED]> wrote:
Guys,
This is the one which originated the changes in the parent Test class
for Entity Manager, but somehow we managed to forget it :-) So, after
discussing the approaches, I did a new diff to replace the old one,
Hello,
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
16 matches
Mail list logo
