I for one would like to have something like Envers for Hibernate ;)
/max
Hello,
currently I'm a working for the jboss.org team, but as you maybe
remember I also created the Envers project (http://www.jboss.org/
envers/). I would like to change my scope of work a bit and work
"officialy" o
I'm just a contributor for Search, but if you may be interested in my opinion:
we released software yesterday in production which uses Envers 1.0GA
and it's really being useful.
And I learned in some minutes how to use it :-)
So if I could vote I would definitely make it "officially" part of Hibe
Guys,
Could someone please review the diff attached on EJB-395 ? If it looks good,
I'll commit to trunk and run the tests for all supported databases.
http://opensource.atlassian.com/projects/hibernate/browse/EJB-395
http://opensource.atlassian.com/projects/hibernate/secure/attachment/14215/Chan
Too bad y'all did not isolate the API then :(
It may be confusing to users, but I think we need to stay with
hibernate-jbosscache2. Worst case we can push that this is our "second
attempt" at integration as the reason for the '2'.
-
Steve Ebersole
Project Lead
http://hibernate.org
[EMAIL PROT
I think we should officially move to "inclusion" of JBossCache 3.0 in
3.4 which is not too far off. For 3.3 it is easy enough for users to
override Hibernate's declaration of JBossCache version to use 3.0 via
Maven *provided* the API really is compatible (drop-in replacement
wise)
-
Steve Ebe
Just ran the current trunk testsuite for cache-jbosscache2 using JBC
3.0.0.CR1 and there are no problems.
However, there are a 21 failures trying to use 3.0.0.CR1 in Hibernate
3.3.1. All seem to be due to the removal of the
DefaultCacheFactory.getInstance() method. The failing calls are not i
so JBC 3 needs this change anyway? at which point it would be a total
drop-in replacement?
Just want to make sure i fully understand.
-
Steve Ebersole
Project Lead
http://hibernate.org
[EMAIL PROTECTED]
Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.co
Steve Ebersole wrote:
so JBC 3 needs this change anyway?
Yes, if it wants to go in, say, JBoss AS 5.2. Which I'm quite sure the
JBC team wants, since they made a bunch of other more significant
changes to ensure compatibility. This one's real trivial.
at which point it would be a total
d
