You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by philipp_s <ps...@qpass.com> on 2008/09/19 11:18:21 UTC

re-registering an enumerated property

Is there a way to change the enumerated values for a property?


e.g. the repository has a property with the following definition:



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sample:state 'new' mandatory
autocreated < 'new', 'old'


but I need to change the definition to something like that:


&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;        sample:state 'new'
mandatory autocreated < 'new', 'old', 'ancient'


when I try to re-register the property I get the following exception:


org.apache.jackrabbit.core.nodetype.NodeTypeConflictException:
{http://www.sample.com/sample}Sample contains ambiguous definitions for
property named {http://www.sample.com/sample}state


is there a way to get around this issue? Or do I need to recreate the
repository?


thx


Philipp

 

-- 
View this message in context: http://www.nabble.com/re-registering-an-enumerated-property-tp19568953p19568953.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: re-registering an enumerated property

Posted by philipp_s <ps...@qpass.com>.
the issue has been created: https://issues.apache.org/jira/browse/JCR-1781

thx,

Philipp



Jukka Zitting wrote:
> 
> Hi,
> 
> On Fri, Sep 19, 2008 at 11:18 AM, philipp_s <ps...@qpass.com> wrote:
>> Is there a way to change the enumerated values for a property?
> 
> Not currently. I think we could fairly easily add support for relaxing
> the property constraints (for example by adding new allowed values).
> Can you file a feature request for that?
> 
>> is there a way to get around this issue? Or do I need to recreate the
>> repository?
> 
> Currently you unfortunately need to recreate the repository for such
> changes.
> 
> We already have support for dropping a property definition that isn't
> used anywhere, after that you can add the modified definition. This
> however won't work in your case as your property definition is
> mandatory.
> 
> BR,
> 
> Jukka Zitting
> 
> 

-- 
View this message in context: http://www.nabble.com/re-registering-an-enumerated-property-tp19568953p19777660.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.


Re: re-registering an enumerated property

Posted by philipp_s <ps...@qpass.com>.
Thanks for the info, I am going to file a request.

Philipp



Jukka Zitting wrote:
> 
> Hi,
> 
> On Fri, Sep 19, 2008 at 11:18 AM, philipp_s <ps...@qpass.com> wrote:
>> Is there a way to change the enumerated values for a property?
> 
> Not currently. I think we could fairly easily add support for relaxing
> the property constraints (for example by adding new allowed values).
> Can you file a feature request for that?
> 
>> is there a way to get around this issue? Or do I need to recreate the
>> repository?
> 
> Currently you unfortunately need to recreate the repository for such
> changes.
> 
> We already have support for dropping a property definition that isn't
> used anywhere, after that you can add the modified definition. This
> however won't work in your case as your property definition is
> mandatory.
> 
> BR,
> 
> Jukka Zitting
> 
> 

-- 
View this message in context: http://www.nabble.com/re-registering-an-enumerated-property-tp19568953p19669624.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.


Re: re-registering an enumerated property

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Fri, Sep 19, 2008 at 11:18 AM, philipp_s <ps...@qpass.com> wrote:
> Is there a way to change the enumerated values for a property?

Not currently. I think we could fairly easily add support for relaxing
the property constraints (for example by adding new allowed values).
Can you file a feature request for that?

> is there a way to get around this issue? Or do I need to recreate the
> repository?

Currently you unfortunately need to recreate the repository for such changes.

We already have support for dropping a property definition that isn't
used anywhere, after that you can add the modified definition. This
however won't work in your case as your property definition is
mandatory.

BR,

Jukka Zitting