You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org> on 2010/03/25 16:35:27 UTC
[jira] Created: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
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
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.
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
Posted by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850122#action_12850122 ]
Dhrubojyoti Kayal commented on OCM-43:
--------------------------------------
I will try to remove that.
But recently tried that while running a Spring embeded Jr based web app on tomcat it did not work
> 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.
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
Posted by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850132#action_12850132 ]
Dhrubojyoti Kayal commented on OCM-43:
--------------------------------------
Will try in the weekend to make it maven compatible
> 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.
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Posted by "Kadir Alaca (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kadir Alaca updated OCM-43:
---------------------------
Attachment: jackrabbit-ocm-1.5.3-upgrade-to-2.1.1.patch
Here is a patch to upgrade OCM to JCR 2.0 with running tests.
It contains also fixes for all deprecated API usage but for XPATH and SQL.
> 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: 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.
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850130#action_12850130 ]
Jukka Zitting commented on OCM-43:
----------------------------------
I can't commit the patch as is, since it causes compile failures (either in src/main if the POM is not updated, or in src/test otherwise). It would be great if you could update the patch so that the default "mvn clean install" build in svn trunk works without problems.
> 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.
[jira] Updated: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Posted by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dhrubojyoti Kayal updated OCM-43:
---------------------------------
Status: Patch Available (was: Open)
I have removed all compilation problems
Changed classes which had dependencies on the old JR code base to JR 2 code base
Added an image showing the jar dependencies to compile this project
> 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
> 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.
[jira] Updated: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Posted by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dhrubojyoti Kayal updated OCM-43:
---------------------------------
Attachment: ocm.zip
ocm.patch
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
Posted by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850125#action_12850125 ]
Dhrubojyoti Kayal commented on OCM-43:
--------------------------------------
I checked the patch
Looks fine to me
Once it is in svn i will download, make necessary changes in POM and test classes which were not compiling and submit another patch
> 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.
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
Posted by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850481#action_12850481 ]
Dhrubojyoti Kayal commented on OCM-43:
--------------------------------------
+ Maven enabled project uploaded
+ patch file uploaded
Note all the source files including the test sources compiles and work
Maven dependencies resolved check if they are correct in version w.r.t to other projects
Also at present some of the tests fail, will correct them and add few more in due course of time.
> 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.
[jira] Updated: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (OCM-43) Reviving OCM framework with Jackrabbit
2.x
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (OCM-43) Reviving OCM framework with Jackrabbit 2.x
Posted by "Dhrubojyoti Kayal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dhrubojyoti Kayal updated OCM-43:
---------------------------------
Attachment: jar-dependencies.jpg
src.zip
Source file with the compilation errors removed + incompatible classes removed
An image file showing the jar dependencies to compile this project.
> 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, 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.