[
https://issues.apache.org/jira/browse/JCRVLT-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562233#comment-17562233
]
Konrad Windszus edited comment on JCRVLT-628 at 7/4/22 4:36 PM:
----------------------------------------------------------------
There are three solutions here:
# Either we throw an exception during construction for type =
PropertyType.UNDEFINED or
# we defer throwing until the property is serialized or
# we just don't emit type information for type = PropertyType.UNDEFINED during
serialization (deserialization into repo will just call
{{Node.setProperty(String key, String value)}} in that case, which means that
the repo figures out the according type depending on the nodes effective type.
was (Author: kwin):
There are three solutions here:
# Either we throw an exception during construction for type =
PropertyType.UNDEFINED or
# we defer throwing until the property is serialized or
# we just don't emit type information for type = PropertyType.UNDEFINED during
serialization
> Wrong type information emitted for undefined DocViewProperty type
> -----------------------------------------------------------------
>
> Key: JCRVLT-628
> URL: https://issues.apache.org/jira/browse/JCRVLT-628
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: 3.6.2
>
>
> In case DocViewProperty(2) is created with the undefined type the
> serialization should not include a type information either but currently it
> emits
> {code}
> "{undefined}myvalue"
> {code}
> instead.
> Prior to JCRVLT-516 the docviewproperty was not allowed to be created with
> undefined type (as it was using
> https://developer.adobe.com/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Property.html#getType()).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
