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" on Envers. But, as the logical place to do this would be
in hibernate, this
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
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.
Great to know it's being used :)
And I learned in some minutes how to use it :-)
So if I could vote I would defin
But, as the logical place to do this would be in hibernate, this
brings the question: would you (= the Hibernate team) be interested
in Envers and in me developing it further? :)
I'll take the lack of answers as a no :) But thanks, Max and Sanne :)
Meanwhile, maybe it will interest some of yo
I'd say yes most definitely...
One thing I would like to see in adition is the ability to store
flattened audting of changes. There are many examples of such a thing
on the wiki and the web at large.
-
Steve Ebersole
Project Lead
http://hibernate.org
[EMAIL PROTECTED]
Principal Software Engi
Hello,
One thing I would like to see in adition is the ability to store
flattened audting of changes. There are many examples of such a thing
on the wiki and the web at large.
yes, that's one of the points on my roadmap - "support for different
versioning schemes" (provided I have the time to
I think the "plug in the way versioned data is stored" bit accounts for
what I meant :)
Also I suggest that you move away from the term "versioning" here. This
is already:
1) over-used/over-loaded
2) used by the JPA spec to mean optimistic locking.
Really this is "auditing" or "capturing histori
I can see the confusion. Hibernate has a similar annotation for
optimistic locking which nearly matches "Versioned" in Envers.
Some "Version"-free class naming ideas:
RevisionListener
VersionsReader -> RevisionReader | HistoryReader
Classes
DefaultRevisionEntity
VersionsReaderFactory -> RevisionR
I wonder if it really has to be a project on its own?
A module in core would make more sense?
--
Emmanuel Bernard
http://in.relation.to/Bloggers/Emmanuel | http://blog.emmanuelbernard.com
| http://twitter.com/emmanuelbernard
Hibernate Search in Action (http://is.gd/Dl1)
On Oct 21, 2008, at 1
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 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
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
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
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
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
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
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
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
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
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
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
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
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
Hello,
I'd say either @Audited or @Historized. @Audited sounds more
"natural"
to me, but like I said above I think @Historized is more "correct".
the dictionary has a similar word - historicized - that me means to
"render historic".
But having a @Historicized annotation doesn't seem very
@StoreHistory
@KeepHistory
I probably like @Audited better though.
--
Emmanuel Bernard
http://in.relation.to/Bloggers/Emmanuel | http://blog.emmanuelbernard.com
| http://twitter.com/emmanuelbernard
Hibernate Search in Action (http://is.gd/Dl1)
On Oct 24, 2008, at 06:59, Adam Warski wrote:
On Fri, Oct 24, 2008 at 5:00 PM, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
> @StoreHistory
> @KeepHistory
>
> I probably like @Audited better though.
@Historized sounds computer science-y and pretty cool. @Chronicled is
also pretty cool sounding.
"Audit" is right out. It means: "1 a: a formal e
@KeepHistory sounds well, it's straightforward to what it's going to do.
I was thinking about @TrackChanges but you aren't really building "diff"s,
so "history": @TrackHistory or @KeepHistory ?
still including some flavour of the "version" should be better IMHO,
as every programmer
has some knowl
On Oct 24, 2008, at 22:22, Elias Ross wrote:
On Fri, Oct 24, 2008 at 5:00 PM, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
@StoreHistory
@KeepHistory
I probably like @Audited better though.
@Historized sounds computer science-y and pretty cool. @Chronicled is
also pretty cool sounding.
"Au
I like @TrackHistory
/max
@KeepHistory sounds well, it's straightforward to what it's going to do.
I was thinking about @TrackChanges but you aren't really building
"diff"s,
so "history": @TrackHistory or @KeepHistory ?
still including some flavour of the "version" should be better IMHO,
a
Generally annotations on an entity are describing a quality of the
entity, whereas a lot of these suggestions are describing actions to be
done with or on behalf of the entity (e.g., its @Entity not
@StoreInDatabase, its @Version not @UseToOptimisticlyLock, its @Id not
@TrackIdentifierValue, etc).
The term 'audit' here is fairly well excepted in our field to mean
exactly what we are talking about here.
And besides, you cant use the dictionary to dismiss one possibility in
favor of another that does not even exist in the dictionary ;)
-
Steve Ebersole
Project Lead
http://hibernate.org
I know, but I still like it ;)
/max
Generally annotations on an entity are describing a quality of the
entity, whereas a lot of these suggestions are describing actions to be
done with or on behalf of the entity (e.g., its @Entity not
@StoreInDatabase, its @Version not @UseToOptimisticlyLock, i
33 matches
Mail list logo
