[
https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated OCM-43:
-----------------------------
Attachment: OCM-43.patch
Thanks for the work! I merged the source zip you attached with the latest OCM
trunk in svn and came up with the attached patch. Can you check that I got all
your changes? It would be easier to review your changes if you submitted
them as patches against the latest svn trunk.
To make the changes compile I had to upgrade the jackrabbit-core dependency to
2.0.0 in the POM. However, then
some of the test cases in src/test/java didn't compile anymore. Have you
already looked at that code too?
> 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.
