[
https://issues.apache.org/jira/browse/SLING-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958885#comment-15958885
]
Konrad Windszus commented on SLING-4043:
----------------------------------------
The setup is a bit weird right now:
We have for the UI model
# {{GenericJcrRootFile}}, constructed from {{IFile}} for all FileVault files
# {{DirNode}}, constructed from {{IResource}}
# {{SyncDir}}, for the entry {{IResource}}
In addition we have {{ResourceProxy}} which in general can be constructed from
{{IResource}} as well. Currently the {{ResourceProxy}} can be serialized to
e.g. the FileVault format. In addition {{GenericJcrRootFile}} s can be
serialized as well.
I would propose to make all {{JcrNode}} s just a thin layer around a
{{ResourceProxy}}, and get rid of the parsing/serializiation functionality in
{{GenericJcrRootFile}}.
[~rombert] WDYT?
> The JCR properties view does not display escaped properties with escaped
> values correctly
> -----------------------------------------------------------------------------------------
>
> Key: SLING-4043
> URL: https://issues.apache.org/jira/browse/SLING-4043
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.2
> Reporter: Robert Munteanu
> Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.2.0
>
>
> Consider a property serialized as
> {noformat}org.apache.sling.commons.log.pattern="\{0,date,yyyy-MM-dd
> HH:mm:ss.SSS} {4} [{3}] {5}"{noformat}
> The value displayed by the JCR properties view is {noformat}{4} [{3}]
> {5}{noformat}, while the value displayed when editing is
> {noformat}\{0,date,yyyy-MM-dd HH:mm:ss.SSS} {4} [{3}] {5}{noformat}
> In fact, both the display and edit modes should work with the unescaped value
> {noformat}{0,date,yyyy-MM-dd HH:mm:ss.SSS} {4} [{3}] {5}{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
