jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Lombart (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1467) Hide ugly repository init code for OCM
Date Thu, 13 Mar 2008 21:10:25 GMT

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

Christophe Lombart resolved JCR-1467.

    Resolution: Fixed

I made patch. Can you check it ? 

It is no longer necessary to use the ocm namespace and the ocm:discriminator mixin type. 

Here is a summary of the current situation  : 

1. If the jcr node type is map to only java class, it is always possible to find the class
name to instantiate. So, a discriminator (an extra property which will contains the class
name) is not necessary.

2. if the same node type is mapped to different java classes, we have different situations
a. If the class is mapped to the unstructured node type or a node type
that gives you  the possibility to add extra properties, OCM will create a new
property "ocm_classname".
b. If it  is not possible to add this property due to strong constrains in the corresponding
node type, OCM will try to add the mixin type "ocm:discriminator".

> Hide ugly repository init code for OCM
> --------------------------------------
>                 Key: JCR-1467
>                 URL: https://issues.apache.org/jira/browse/JCR-1467
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: jackrabbit-ocm
>         Environment: All
>            Reporter: Alex Lukin
>            Assignee: Christophe Lombart
>             Fix For: 1.5
>         Attachments: jackrabbit-OCM-repoinit.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Hide repository namespace registration and ocm:discriminator node type registration in
implementation of OCM

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message