jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Kennedy <da...@us.ibm.com>
Subject Re: Override property protected attribute
Date Tue, 19 Sep 2006 19:39:51 GMT
"Nicolas " <ntoper@gmail.com> wrote on 09/19/2006 03:24:22 PM:

> I didn't develop something like this for the backup tool. What I did was
> adding a flag in the PropInfo class for this purpose.
> As Stefan wrote: "no. great care has been taken so far to avoid 
loopholes in
> the core in order to prevent security/data consistency issues."

I agree that it is a loophole, but at the same time there are many use 
cases where it is needed (e.g. external migration (re: export/import), 
replication/syndication, archive/restore, etc.)  Ideally the capability 
would be provided with security...ala a restricted set of administrative 
users or administrative sessions)

> It seems your issue is a lot more common than expected: sometimes, we 
> to escape protected checks. Maybe we should add the flag you describe 
> allow it only for custom node types.
> If you can create consensus on this, I would be happy to help you on 
> Actually, it would ease the backup tool's life a lot.
> What do you think?
> Nico
> my blog! http://www.deviant-abstraction.net !!
> On 9/19/06, David Kennedy <davek@us.ibm.com> wrote:
> > What I'm really looking for is something as simple as a flag/bit on 
> > setProperty methods (e.g. setProperty(propertyName, Value,
> > overrideProtected)).  Importing an XML stream may be a little too
> > heavyweight for my usage.
> >
> > David

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