[
https://issues.apache.org/jira/browse/JCRVLT-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCRVLT-698:
----------------------------------
Description:
Currently, vault allows changing primary types - but this only works in
practice when the content after import actually conforms to the new type
definition. Thus, using a new type that is more restrictive may fail later on
when the session is saved.
A new mode could allow removing or moving away child items that conflict with
the new type definition, but this will likely need to be an opt-in.
Furthermore, this would require replicating node type internals from the JCR
implementation - instead, we could also consider exposing more information from
the JCR implementation, such as listing conflicting child nodes (throug an
extension API).
was:
Currently, vault allows changing primary types - but this only works in
practice when the content after import actually conforms to the new type
definition. Thus, using a new type that is more restrictive may fail later on
when the session is saved.
A new mode could allow removing or moving away child items that conflict with
the new type definition, but this will likely need to be an opt-in.
Furhermore, this would require replicating node type internals from the JCR
implementation - instead, we could also consider exposing more information from
the JCR implementation, such as listing conflicting child nodes (throug an
extension API).
> allow primary nodetype updates that make the node more restrictive
> ------------------------------------------------------------------
>
> Key: JCRVLT-698
> URL: https://issues.apache.org/jira/browse/JCRVLT-698
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Reporter: Julian Reschke
> Priority: Major
>
> Currently, vault allows changing primary types - but this only works in
> practice when the content after import actually conforms to the new type
> definition. Thus, using a new type that is more restrictive may fail later on
> when the session is saved.
> A new mode could allow removing or moving away child items that conflict with
> the new type definition, but this will likely need to be an opt-in.
> Furthermore, this would require replicating node type internals from the JCR
> implementation - instead, we could also consider exposing more information
> from the JCR implementation, such as listing conflicting child nodes (throug
> an extension API).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
