On Fri, 2008-01-11 at 17:34 +0100, Jörn Nettingsmeier wrote: ... > but a lesson could be learnt from this nonetheless: we should try to tie > into apache (and other projects we re-use) more than we currently do,
Can you define tie in? ... > > i'm sure JCR will be re-considered (although i would also like to bring > eXist into the discussion). Actually a while back we decided to go our own route for jcr like with some other components such as workflow markup, ac, ... My opinion about this is, it is total overkill and inefficient. We need to maintain too much medium quality code that is not even lenya specific to solve common problems that are already solved by specialized OS products. See the Jboss workflow engine that is getting used in e.g. Daisy and Alfresco and compare it with ours. Much more powerful, tools support, ... Our own JCR implementation is just another bullet point in a big list. ...and yes we need jcr, now! A CMS without JCR support is doomed. > but then there's also the move to cocoon > 2.2, blocks and spring - i wonder which should be handled first. I am using cocoon 2.2 and spring in current project and have ported the forrest dispatcher as a cocoon block [1]. Moving to cocoon 2.2 architecture in 2.x of lenya is IMO not a priority since it means a rethinking of many parts of our current use of cocoon. > then there's people who feel that lenya should become more independent > of cocoon (thorsten and andreas, if i have understood them correctly), Of the underlying Avalon dependencies yes, further cocoon 2.2 tries to be more standard like and moving it to spring brings a lot more flexibility. However my point is that I would like to see that I can interact with lenya fully via an java api or having the possibility to switch to another interface. JSF is e.g. IMO the way better interface in comparison with cforms. The question is to have a clean API to be able to switch technologies. A small nice java based core and wrapper for cocoon, jsf, tapestry, ... > and others (well, me) that think that lenya should become more > cocoon-ish and expose and handle more stuff through sitemaps and > pipelines than it currently does. Well, the sitemaps and pipeline handling has slightly changed in cocoon 2.2. e.g. the pass-through attribute does not exist anymore for a mount. For e.g. forrest that is a big problem since we use a lot of pass-throughs. ...but what do you mean with: expose and handle more stuff through sitemaps and pipelines than it currently does. can you give an example? > > lots of stuff to do for a small community... Yes, we need all the help we can, but slimming down our core and outsource components as dependencies such as JCR and workflow and ... will reduce the workload. salu2 [1] http://svn.apache.org/repos/asf/forrest/trunk/whiteboard/cocoon-2.2-blocks/ > > Andreas Hartmann wrote: > > Hi Lenya devs, > > > > FYI: > > > > http://www.theserverside.com/news/thread.tss?m=c.reply&thread_id=48070#245093 > > > > <quote> > > Total frustration with competing apache projects!!! For some unknown > > reason apache projects always have competing and incompatible projects. > > The Lenya and Jackrabbit is just an obvious one! If the JSR standard has > > been approved and apache promotes to be a top domain project then WHY do > > they not have some say about minimum compatibility! > > > > This is beyond me! Any other company or organization will make great > > efforts to ensure the value of one product can be used by other > > products! If I download JBoss Portal I feel quite confident that it will > > work with JBoss AS. Maybe it just me but at some time I would like to > > see some real up life for organizations and not a major integration, > > redundant solution approach!! > > > > I like the given features of Lenya but also would like my CMS repository > > to be JSR compliant so I can access with other tools such as BPM engines > > or WebDav compliant applications. > > > > So all that being said… why does Lenya community think that JR > > integration is not important? And continue to support a proprietary API? > > And why do they not understand that a CMS system is a central part to > > most organizations infrastructure!! > > > > Do other developers out there feel the same way?? > > </quote> > > > > -- Andreas > > > > > -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
