jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-380) Define conversion of property values
Date Fri, 19 Oct 2012 12:22:13 GMT

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

Jukka Zitting commented on OAK-380:

To start with I'm not too excited about having JCR value types present in oak-core. I'd rather
just deal with JSON types (with default JavaScript type conversions) at this level and leave
more complex typing to oak-jcr and the various JCR-related plugins we have.

Anyway, since we now do have JCR values types in oak-core, I think it would make sense to
also support JCR value conversions directly through the API instead of a separate utility
class. However, I'd still exclude all name mappings from oak-core.
> 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