Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Invalid
-
None
-
None
-
None
Description
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.
--------------------------------------------------
int UNDEFINED
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.