[ 
https://issues.apache.org/jira/browse/JCRVLT-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated JCRVLT-516:
-----------------------------------
    Description: Currently {{DocViewProperty}} can only be generated based on 
Property objects or on the string representation. To be able to also generate 
the string representation when generating DocView files outside of a JCR 
repository context it would be nice to add additional constructors or static 
format methods which act on parameters which are easier to create outside a 
repository context (e.g. String, or Map<String, Object>)  (was: Currently both 
{{DocViewNode}} and {{DocViewProperty}} can only be generated based on 
Node/Property objects or on the string representation. To be able to also 
generate the string representation when generating DocView files outside of a 
JCR repository context it would be nice to add additional constructors or 
static format methods which act on parameters which are easier to create 
outside a repository context (e.g. String, or Map<String, Object>))

> Ease usage of DocViewProperty outside a repository context
> ----------------------------------------------------------
>
>                 Key: JCRVLT-516
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-516
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: vlt
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: 3.4.12
>
>
> Currently {{DocViewProperty}} can only be generated based on Property objects 
> or on the string representation. To be able to also generate the string 
> representation when generating DocView files outside of a JCR repository 
> context it would be nice to add additional constructors or static format 
> methods which act on parameters which are easier to create outside a 
> repository context (e.g. String, or Map<String, Object>)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to