Hi Lenya devs, in the Cocoon community there seems to be a certain interest in extending the JCR block signatures to leverage JCR functionality.
A valid approach seems to be to implement the repository block interfaces, especially - InspectableSource (adding properties to sources) - VersionableSource - LockableSource This would mean that the repository block components (especially RepositorySource) could be used to access a JCR repository. A benefit of this approach is that Cocoon would provide a generic repository access API. If our o.a.lenya.cms.cocoon.source.RepositorySource implemented these interfaces as well, we could use the Cocoon repository block API throughout Lenya, and switch between our repo implementation and the JCR block. +-----------------------------------------------------+ | Lenya usecases etc. | +-----------------------------------------------------+ | Cocoon repository block | +-----------+-+-----------------+---------------------+ | JCR block | | Lenya repo impl | ... +-----------+ +-----------------+ Advantages: - We would do things the Cocoon way. - As soon as the JCR block is stable, we can drop all Lenya repository code. - We don't have to care for JCR integration at all (the only notion of "JCR" in Lenya would be a declaration in cocoon.xconf). Disadvantages: - We have to live with the repository block API. - We lose direct control over the repository API. As a comparison, the approach that we followed up to now: +-----------------------------------------------------+ | Lenya usecases etc. | +-----------------------------------------------------+ | Lenya repository interfaces | +----------------+-+-----------------+----------------+ | Lenya JCR conn | | Lenya repo impl | ... +----------------+ +-----------------+ | JCR block | +----------------+ WDYT? -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
