You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2012/04/27 12:43:49 UTC

[jira] [Commented] (OAK-16) Proper ValueFactory implementation and Value handling

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

angela commented on OAK-16:
---------------------------

the refactoring is almost completed. nevertheless i would like to keep the issue until we 
have the reference values implemented (and properly validated) as well.

in addition there are still some value related tck test failing. some of those 
may be caused by missing validation either on oak-jcr or on oak-core... i need to take
a closer look at this again.
                
> Proper ValueFactory implementation and Value handling
> -----------------------------------------------------
>
>                 Key: OAK-16
>                 URL: https://issues.apache.org/jira/browse/OAK-16
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: angela
>
> the GlobalContext contains the following code:
>         put(ValueFactory.class, new SimpleValueFactory());
> that doesn't work as the ValueFactory needs to be bound to each session instance
> in order to be able to deal with namespace mappings, paths, names etc....
> michi, just told me that in addition the ValueConverted needs some focus as well.
> and yesterday, i saw that Property#getType implementation in the jackrabbit-mikrokernel
> was not correct... 
> just to mention a few issues....

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira