You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/03/26 13:38:27 UTC
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850117#action_12850117 ]
Jukka Zitting commented on OCM-43:
----------------------------------
PS. Ideally I'd like to see the direct jackrabbit-core dependency removed entirely from OCM. With JCR 2.0 it should no longer be necessary for the code to depend on Jackrabbit internals.
> Reviving OCM framework with Jackrabbit 2.x
> ------------------------------------------
>
> Key: OCM-43
> URL: https://issues.apache.org/jira/browse/OCM-43
> Project: Jackrabbit OCM
> Issue Type: Improvement
> Environment: Jackrabbit 2.x
> Reporter: Dhrubojyoti Kayal
> Attachments: jar-dependencies.jpg, OCM-43.patch, src.zip
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The OCM framework currently does not work with Jackrabbit 2.x. This is an excellent framework and allows developers to work with the beans without worrying much about the internal details of working with Nodes and associated Jackrabbit internal classes like session. This is very much in line with ORM and DAO patterns. This allows quick application development and roll out of new entities in the system real easy.
> Tasks required
> + Remove the compilation problems
> + Change/remove the dependencies on old classes and libraries/jars
> + Test
> + Document
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.