Andreas Hartmann schrieb:
(...)(a) Lenya should focus on JCR only. It is OK to implement core functionality which absolutely relies on JCR features.(...) - Is this sufficient? Can we require people to implement JCR to access custom repositories?
What is meant here with access to custom repositories ? If it's integrating external sources, that IMO has no effect on Lenya/JCR: if you want the CMS to manage that source, it's no longer external and it would instead need to be imported. If instead you want data managed elsewhere to be displayed within a publication, this also wouldn't be affected by Lenya switching to JCR
So IMO this question is not applicable
- Is Jackrabbit stable enough to act as the default Lenya repository implementation?
I agree that's a valid concern. I guess, from the community perspective, we have to try :) An alternative scenario is to base Lenya's content handling on the JCR API anyway (meaning, a Lenya node becomes a JCR node etc.) and for storage have our content mapped one-to-one onto files, as it is now.
If these concerns are not considered weighty, we should start to re-design the Lenya repository layer. IMO it makes sense to use a Wiki page to collect random thoughts and to refine them gradually. Of course a meeting (brainstorming day) would be great. Maybe all involved people want to visit Zurich? :)
I'd be interested in that. I'm coming to Zurich anyway on a personal matter Sept. 24-25, so let me be the first to propose a date ;)
How about monday, Sept. 26th ? -- Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
