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] Commented: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Date Mon, 12 Apr 2010 07:59:41 GMT

    [ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855881#action_12855881
] 

Jukka Zitting commented on OCM-43:
----------------------------------

Any update on the failing tests?

PS. Quite a large part of the patch is just reformatting the code, which makes it difficult
to review the exact changes you've made. It looks like the reformatting is for the better,
so if it's not too much trouble, it would be great if you could create a separate patch for
just the formatting changes. I can commit that without waiting for the unit tests to be fixed.

> 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, 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message