3 Apr
2007
3 Apr
'07
7:08 p.m.
Hi Christophe,
Does your email means you're proposing to implement this? (I'm
referring to the "Proposal" in the subject line)
Also you did not describe how to implement what you suggest. Could
you be more specific?
If I understand your email, you're suggesting to decouple document
state from document storage. For example, document's content could
still be managed using XWikiHibernateStorage but document's states
could be managed by, say some custom tool. Hmm.... I'm not entirely
convinced. I think it'll raise several issues, one of which is
distributed transactions. Another one is performances.
To implement your use case you could also intercept document save
using the XWiki Notification Service and save your own document state
as you want it.
Not sure exactly what you're looking for with your email...
Thanks
-Vincent
On Apr 3, 2007, at 6:42 PM, Christophe Koehl wrote:
Hello the xwiki community,
We use Xwiki for a couple of years now as a tool for managing our IT
projects.
During the redaction of the main project documents, we have a strong
need of versionning management - not the xwiki system, but our own
one.
To be clear, when a wiki page is written some information can be
included in it :
* Document version
* Name of the redactor
* Date of the modification
* Name of validator
* Comment
In fact, the xwiki system contains almost all the components, but
those
information are updated each time a modification is being done, even
when the document is a draft and has not be validated.
For example, the xwiki version number is automatically incremented
whereas the real document version number is still the same.
So it can very very useful to integrate a system which can be able to
manage manually the different state of the document.
Regards
Christophe Koehl
From - Mon
.org/wws