Michi wrote: > Flexibility doesn't mean we have to implement all scenarios, but > provide interfaces which allow various scenarios.
Sure. The Interface you are looking for is called "Jackrabbit backend". Think reuse here! Regards, Torsten > Andreas Hartmann wrote: > >> Michael Wechner wrote: >> >>> Andreas Hartmann wrote: >>> >>>>> >>>>> If you want to use Lenya to edit the content of an XDoc Apache >>>>> website, >>>>> you need the latter, don't you? The structure is given and you >>>>> would even >>>>> have to support a different way of handling the sitemap, which >>>>> would no >>>>> longer be Lenya's sitemap.xml but Forrest's site.xml. (Which is >>>>> sort of >>>>> pseudo-XML which will make it pretty funny IMO.) Ok, the Doco project >>>>> might have sorted that all out. Again, apologies for not keeping up >>>>> with >>>>> the discussion here. >>>> >>>> >>>> >>>> >>>> With the current Lenya 1.4, this would mean to implement a custom >>>> DocumentIdToPathMapper and a custom SiteManager. >>>> >>>> But - do we really want to allow editing a Forrest site? >>> >>> >>> sure. No offense, but if Lenya isn't able to do this, then Lenya is >>> pretty useless. If Lenya doesn't allow building a Forrest publication, >>> then I think we have totally missed the goal of providing a Content >>> Management Framework >> >> >> I don't think that we will be able to support all existing content >> storage mechanisms. > > > the framework should be flexible enough that one is able to implement > it's own content storage. It's the same with URL spaces .... > >> We should be careful not to lose ourselves in >> flexibility. We can't foresee all scenarios anyway. > > > Flexibility doesn't mean we have to implement all scenarios, but > provide interfaces which allow various scenarios. I guess the minimal > interface would be > > InputStream getInputStream > OutputStream getOutputStream > >> A framework is >> not a Swiss army knife. > > > why not? > >> >> For special scenarios, special solutions can be found. >> >> In the case of Forrest - how about implementing a custom generator >> which provides a read-only view of the Lenya repository which resembles >> the Forrest file system? > > > I think Lenya should be able to read and write to Forrest. Again no > offense > and please apologize for sounding harsh, but I think if Lenya is not able > to provide such interfaces it's really useless. > > Michi > >> That would only require one change to the >> Forrest application (re-configuring the file generator). >> >> -- Andreas >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Michael Wechner > Wyona - Open Source Content Management - Apache Lenya > http://www.wyona.com http://lenya.apache.org > [EMAIL PROTECTED] [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
