jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Date Thu, 30 Sep 2010 12:57:08 GMT

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

Jukka Zitting updated OCM-43:
-----------------------------

           Status: Resolved  (was: Patch Available)
         Assignee: Jukka Zitting
    Fix Version/s: 1.6.0
       Resolution: Fixed

Thanks, Kadir! I committed the latest patch in revision  1003049.

> 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
>            Assignee: Jukka Zitting
>             Fix For: 1.6.0
>
>         Attachments: jackrabbit-ocm-1.5.3-upgrade-to-2.1.1.patch, jar-dependencies.jpg,
OCM-43.patch, ocm.patch, ocm.zip, 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.


Mime
View raw message