[
https://issues.apache.org/jira/browse/OCM-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849628#action_12849628
]
Thomas Pasch commented on OCM-41:
---------------------------------
See http://wiki.apache.org/jackrabbit/OCMandJackrabbit2 :
Starting from version 1.6 OCM source tree is in separate project outside of
main Jackrabbit source.
SVN repository of Commons components can be found at:
https://svn.apache.org/repos/asf/jackrabbit/commons/
SVN of OCM is: https://svn.apache.org/repos/asf/jackrabbit/commons/ocm/
Code examples
No working example yet here but you can use old examples from
http://jackrabbit.apache.org/object-content-mapping.html
OCM code depends only on JSR 170 or JSR 283 API so everything must work well.
Features that do not require "descriminator" node type registartion seems to
work. Complex class maping requires registration of additional node type.
Node type registration is changed slightly in 2.0 so you need to change
"NodeTypeDef" to "QNodeTypeDefinition" in node type registration code.
> Jackrabbit OCM is dead after 1.5.3 or wat?
> ------------------------------------------
>
> Key: OCM-41
> URL: https://issues.apache.org/jira/browse/OCM-41
> Project: Jackrabbit OCM
> Issue Type: Improvement
> Reporter: Sreekanth S Nair
>
> Please lets know the status of jackrabbit OCM support, is dead or alive?
> Since OCM is comparatively easy to implement.. haven't seen any further good
> news in OCM library after 1.5.3 release.
> Please let us know, continuing development in OCM is a good idea or stick to
> the old JCR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
