jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-380) Define conversion of property values
Date Fri, 19 Oct 2012 11:42:13 GMT

    [ https://issues.apache.org/jira/browse/OAK-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479965#comment-13479965

Michael Dürig commented on OAK-380:

After a 2nd though, it might make sense to extend these conversions to all JCR types. That
way we'd have a single place where the conversions are defined and which could be used from
other code as well. Note, that even then conversions involving name/path mappings would still
have to be made explicitly. When done through the {{PropertyState.getValue()}} methods such
conversions would either fail or use a default name/path mapping (preferences?). 

> Define conversion of property values
> ------------------------------------
>                 Key: OAK-380
>                 URL: https://issues.apache.org/jira/browse/OAK-380
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
> i just run into the situation of converting a propertystate's value
> of type Date to a Long, which currently throws numberformatexception.
> while i can work around this, i think we should come up with a clear
> definition on value conversion provided by oak-api. the only thing i
> found so far was the description in PropertyState#getValue that claims
> that a conversion in done but not which conversions are supported.
> unless otherwise specified i had silently expected that simple jcr-conversions
> would work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message