jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "harvey waters" <harvey.wat...@googlemail.com>
Subject Re: Audit Trail
Date Wed, 04 Jul 2007 11:06:21 GMT
Thanks for the comments david.

Our other concern is around the transation managment, we're using an Open
Source stack tomcat/spring/springmodules/acegi/jackrabbit. The audit trail
requires that all our write operations are held in a transaction. Now I know
that JackRabbit supports transactions but has anyone got an open source
stack to actually work with transactions or would it be better if I deployed
jackrabbit into a full blown application server ? On ServerSide you
described JackRabbit as a bit 'rough around the edges' I'm kinda hoping your
not including transaction management in that ?

On 7/4/07, David Nuescheler <david.nuescheler@gmail.com> wrote:
> hi harvey,
> > We decided against it initially because the data is very simple and
> would't
> > require the overheads of versioning, security checking etc.
> the overhead of versioning and security checking etc. really only applies
> if it is used, so for example a node that is not versionable does not
> have versioning
> overhead. security probably might be an issue when it comes to read access
> to the audit trail, who knows...
> i think one should look at these features of a content repository as
> services that
> are exposed by the repository and if unused do not necessarily cause
> overhead,
> but can come in very handy when they become necessary.
> we actually decided to store our applications audit trail in the
> repository and i dont
> regret it. but i guess it all depends on data volume and the usecases in
> the
> application.
> regards,
> david

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message