Suggestion regarding: org.apache.jackrabbit.Constants

[Angela Schreiber <an...@day.com>]

the Constants interface that is now present in
the jackrabbit-commons project contains one String
constant

IMPERSONATOR_ATTRIBUTE

that is possibly a leftover that may not be
intended to be a 'common' constant.

maybe it would be worth to create a separate interface
for core-related constants?

btw: the constant mentioned in the only one that neither
defines a QName nor is namespace related. all others
have a relationship to 'names'. for the sake of clarity
org.apache.jackrabbit.Constants could be renamed to
NameConstants (in analogy to QueryConstants) and/or
moved to the name package.

gruss
angela

Re: Suggestion regarding: org.apache.jackrabbit.Constants

[Stefan Guggisberg <st...@gmail.com>]

On 7/7/05, Angela Schreiber <an...@day.com> wrote:
> the Constants interface that is now present in
> the jackrabbit-commons project contains one String
> constant
> 
> IMPERSONATOR_ATTRIBUTE
> 
> that is possibly a leftover that may not be
> intended to be a 'common' constant.
> 
> maybe it would be worth to create a separate interface
> for core-related constants?

i moved IMPERSONATOR_ATTRIBUTE to o.a.j.c.security.SecurityConstants.

thanks
stefan

> 
> btw: the constant mentioned in the only one that neither
> defines a QName nor is namespace related. all others
> have a relationship to 'names'. for the sake of clarity
> org.apache.jackrabbit.Constants could be renamed to
> NameConstants (in analogy to QueryConstants) and/or
> moved to the name package.
> 
> gruss
> angela
>