Jon Stevens wrote:
>
> <snip>
> > I picture a future where only one framework exists... there is no need
> > for two. If this will be called Cocoon or Turbine or Whatever doesn't
> > really make any difference for both me and Jon, as long as things are
> > done the way we like and they way you like it.
> >
> > But you have to know the alternatives before choosing the right
> > direction, don't you think? I personally believe that Jetspeed2 should
> > be based on Cocoon2. Of course, I'm biased. But Cocoon2 design fits
> > perfectly in what jetspeed2 needs.
>
> How do you know what Jetspeed2 needs? In other words, I have yet to see a
> real clear direction and agreement from ALL of the Jetspeed people about
> what 2.0 really is. So many people are giving their input and ideas that
> there has yet to be a real clear decision IMHO.
>
It doesn't exist yet: Jestpeed 2 idea is what emerged from the ApacheCon
discussions and is not yet formalized but I can also say that I feel
Cocoon 2 design fits jetspeed 2 needs because a portal is just a
customizable publishing system for page components rather than for
complete pages.
> Even on the homepage of the website, Jetspeed claims to be like 10 different
> products and none of them are actually even finished or close to being
> finished IMHO. Releasing a 2.0 means that there is a feature set that has
> been improved on by adding more features. Not a complete rewrite and
> re-structuring of the design goals of the application. Am I making sense?
>
Yes. It's the website that is not making real sense !
>
> <snip>
> > Jon believes web apps and publishing
> > are independent things, one could have turbine as a servlet filter and
> > cocoon as the proper servlet... I thought about the concept and it works
> > for many things, but not for all.
>
> No, I believe that you would build a "publishing webapp" on top of Turbine.
> That is the disconnect that I don't think you understand quite yet. :-)
>
Cocoon 2 is a publishing application developed on top of Avalon, an
application framework and not a web application framework like Turbine.
Whether Cocoon and Avalon will prove adequate for supporting web
applications like Jetspeed is yet to be seen.
> <snip>
> > Cocoon2 will evolve anyway, but any help is an important way to make
> > convergence quicker and communities bigger and stronger.... in the
> > Apache spirit, a happy community is all that matters, if you use Turbine
> > or Cocoon or both or your own framework, it doesn't matter, as long as
> > this project is alive and kicking.
>
> I agree.
>
> -jon
>
Thanks for your input on this, Jon. I think Jetspeed will need to move
much closer to Turbine in its 1.x implementation and we really need
the advice of ssomeone who really understands the framework to make sure
it's correctly leveraged.
You're sure you don't want to stay on this list ? ;/
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
