David Sean Taylor wrote: > > I would like to suggest that, before even considering an entirely new > Java portal project at Apache Portals, that we first explore the > existing portal's capabilities in providing a light weight portal > deployment. Jetspeed-2, as a Spring component architecture, is capable > of assembling together both full-featured and stripped down portal > deployments. Just a matter of assembling the pieces that you want. > I believe there are some improvements we can make, such as 2nd > non-database implementations of many of the components. > > Have you considered Jetspeed-2 to meet these needs? > I would be interested in hearing your reasons for why not. > If not, I would also like to invite you to working with us as a team > effort in assembling a lightweight Jetspeed portal. > Hmm, but doesn't this approach rule out other portal solutions, like Cocoon? (perhaps I'm missinterpreting this)
What I really would like to approach is more synergy between the two portal solutions at Apache, J2 and Cocoon. Unfortunately I don't know that much about J2; but I could imagine that perhaps we could either use a common base or at least share some components - or, which I would prefer as a final result - merge those two solutions. I guess that both solutions have some parts in common and I also guess that Cocoon might be more flexible in some parts and we have the event mechanism. If we would get all of this somehow into J2, we could just ditch the Cocoon solution :( (Which would make me obsolete...) As a first question, what do you think, would it be possible to run J2 inside of a web framework like Cocoon, where Cocoon is just kind of a proxy? Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
