[
https://issues.jboss.org/browse/ARTIF-618?page=com.atlassian.jira.plugin....
]
Brett Meyer closed ARTIF-618.
-----------------------------
Resolution: Won't Fix
The more I think about this, the more I wonder if the trash is actually a good thing. I
can see an "undelete" action being useful. Since I simply move the node to the
trash tree, metadata/relationships and all, that would be as simple as moving it back out.
Further, the other data stores we're considering (relational DB, etc.) will all need
something similar, even if it's a simple "isDeleted" flag.
Consider replacing the s-ramp-trash with something more performant
------------------------------------------------------------------
Key: ARTIF-618
URL:
https://issues.jboss.org/browse/ARTIF-618
Project: Artificer
Issue Type: Enhancement
Reporter: Brett Meyer
Priority: Minor
Brought up by [~eric.wittmann]
(11:12:44 AM) ewittman: i wonder if the trash is more trouble than it's worth
(11:13:48 AM) ewittman: another approach for auditing of deleted artifacts would be to
simply roll up the artifact history into a journal entry (different jcr tree)
(11:16:02 AM) ewittman: that might be superior in a lot of ways - you could get rid of
all the extra trash query code and whatnot
(11:16:13 AM) ewittman: upgrade path for existing users with trashed artifacts is an
issue
(11:16:30 AM) ewittman: but something you could deal with on startup (journal anything in
/trash)
(11:18:54 AM) ewittman: take the artifact and all its audit entries, and roll all that
info up into some new custom s-ramp jcr node somewhere
(11:19:09 AM) ewittman: get it out of the way but keep all the relevant info necessary
for auditing purposes
Note that ModeShape 4.0 added built-in journaling concepts:
https://docs.jboss.org/author/display/MODE40/Journaling
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)