[
https://issues.apache.org/jira/browse/JCR-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559411#action_12559411
]
Ian Boston commented on JCR-872:
--------------------------------
Sorry to interrupt
Please don't bind to Hibernate, if you do, every other user if Hibernate will
be forced to use the same version of Hibernate or not use Jackrabbit. We
(Sakai) already cant use Alfresco for this reason.
The same goes for binding directly to any implementation that locks the jvm to
a particular version of that jar. We have found the *if* you feel you need a
3rd party caching lib, ehcache is Ok since the API exists, is relatively stable
and doesn't require 1001 other jars.
That being said, I thought that there were plenty of other cache mechanisms in
Jackrabbit that did full management and expiry.
Just to give you an idea of the hibernate issues, it binds to specific aop and
cglib versions.... so does spring....
at the moment Jackrabbit is nice to work with because it doesnt cause any
problems in this area.
All IMHO :)
> Cache framework integration
> ---------------------------
>
> Key: JCR-872
> URL: https://issues.apache.org/jira/browse/JCR-872
> Project: Jackrabbit
> Issue Type: Task
> Components: jackrabbit-ocm
> Reporter: Christophe Lombart
> Attachments: observableCache.patch
>
>
> OCM should work with a cache manager.
> * The Spring frameworks offer a nice solution to integrate an application
> with a cache manager (based on AOP).
> * Which cache framework to use ? oscache, JCS, ...
> * A more detailled proposal is required
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
