Jon Stevens wrote: > I don't even have an idea on how to start to answer him. Someone else wanna > try? How about something like this? > Many things needed to create sites like this are actively developed > under the wings of Apache projects, most notably the Jakarta and XML > projects. But: there are overlaps between the various projects, and > subprojects. Some similar things appear in different places (like: a > webserver's built into Tomcat; there's webdav in Apache 2.0, Tomcat > 4.0, Slide shares goals with Jetspeed). The current Apache projects are product-orientated. Each is meant to be something a user can download and start to use. Since the feature-set of products will naturally overlap, so do some of the technologies. This is not unlike the situation where a spreadsheet product may also have a database component, or a where word processing product may also have templates for business presentations. Since may of the products are now relatively mature, we are now discussing a common library of components that can be shared among Apache subprojects, and other products. Of course, before we can have a component library, we need codebases for the components, so this is a natural evolution. > I know the Java, Jakarta projects are in the process of being merged, > but I sure would like to know what gets merged with what! Suppose, to > be more specific, I'd like to use Apache, Tomcat, Cocoon, Jetspeed to > have a flexible XML-based portal set-up. What's happening is that these products are being transferred to the Jakarta site. No other changes to the Java Apache products are contemplated as part of the transfer. For all intents and purposes, they are all "Jakarta" products now, we just have to update the Web sites to reflect what has already been done. > Suppose, to > be more specific, I'd like to use Apache, Tomcat, Cocoon, Jetspeed to > have a flexible XML-based portal set-up. That sounds like a very good way to go! The general idea is that you should be able to assemble the products to build your own platform. Not unlike the way you might put HTTP, FTP, SMTP, and POP servers from different vendors together to assemble your preferred "Web site" platform. I think you will find that many of these products share developers, and you would have many quick answers to any deployment questions. > The main question is: what could we contribute ? Personalization ? > Workflow ? Management features ? Or are these things being worked on > somewhere where I haven't seen it ? This is an open source community, and anything anyone is really working on is all out in the open. So, if you don't see it, it's probably not being done. A good place to double check is on the Jakarta General mailing list, where we now discuss cross-product and Jakarta-wide issues. The best thing to contribute is what you * want * to contribute. The usual approach is that when you find something that you need is missing, create it and then contribute it back to the community for others to use. Of course, the "creating it" part often involves working with others within the community. If you were able to deploy a super-portal based on Apache, Tomcat, Cocoon, Jetspeed, [and JAMES], and turn that into a framework others could use, that would be quite a contribution right there. Off-hand, I might suggest that you focus on working with the Jetspeed team first, and think of your setup as building on what that product has already started. The essence of open-source is finding a shoulder to stand on ;0) -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel 716 425-0252; Fax 716 223-2506. -- http://www.husted.com/about/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
