jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-115) Nodetype is not preserved during export/import
Date Tue, 26 Apr 2005 11:51:28 GMT
     [ http://issues.apache.org/jira/browse/JCR-115?page=all ]
Stefan Guggisberg resolved JCR-115:

    Resolution: Invalid

the problem is that you are using document view serialization. document view is 'lossy' by
definition, e.g. type information of properties 
is lost. 

see 6.4.2 Document View XML Mapping in the 
jsr 170 specification:
The document view is designed to be more human-readable than the system view, though it achieves
this at the expense of completeness. 

what you want to use is system view serialization,
i.e. Session.exportSystemView().

> Nodetype is not preserved during export/import
> ----------------------------------------------
>          Key: JCR-115
>          URL: http://issues.apache.org/jira/browse/JCR-115
>      Project: Jackrabbit
>         Type: Bug
>   Components: nodetype
>     Reporter: fabrizio giustina
>     Assignee: Stefan Guggisberg

> Property defined with a UNDEFINED property type are not handled correctly during export:
the "real" property type assigned on creation is not preserved.
> If you try to export a Boolean property (which is set as UNDEFINED in configuration)
and reimport it the value returned by getType() will change.
> fron jcr specs:
> ...
> Returns the type of this Property. The type returned
> is that which was set at property creation. Note that
> for some property p, the type returned by
> p.getType() may differ from the type returned by
> p.getDefinition.getRequiredType() only in the
> case where the latter returns UNDEFINED. The type of
> a property instance is never UNDEFINED (it must
> always have some actual type). See 6.2.5 Property
> Types and 6.7.18 Discovery of Constraints on Existing
> Items.
> --------------------------------------------------
> This constant can be used within a property definition (see
> 6.7.6 Property Definitions) to specify that the property in
> question may be of any type. However, it cannot be the
> actual type of any property instance. For example it will
> never be returned by Property.getType and (in level 2
> implementations) it cannot be assigned as the type when
> creating a new property.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message