From: Henri Yandell <bayard <at> generationjava.com> > On Tue, 21 Jan 2003, Steven Noels wrote: > > Andrew C. Oliver wrote: > > > > > project. I do kinda think a project proposal might be premature since > > > the specification isn't public yet. > > > > I was trying not to post the obvious, but yes: this seems largely > > premature. No code, a restricted community, too much committers coming > > from one company, I've seen better proposals being fought over lately. > > Also, possible future integration 'ideas' with some related projects > > would be comforting (Jetspeed, Tomcat, Struts/Tiles, and the Cocoon > > portal framework for a starter). > > Is this different from Tomcat and/or JSTL? If so, how? > > I'm clueless on portlets, but from my 'vague consumer' view, I thought > the JSR was standardising a lot of what Jetspeed does. >
A portlet is both different from a servlet and from a taglib. A portlet is mostly servlet-like but with the following additional requirements: - aggregation aware (outputs only code fragments, supports the notion of a "portal page context" and possible communication between portlets on the same page) - standardized states: for example, Maximized, Minimized, Customization, etc... Not being on the JSR Expert group, I don't have all the details of the forthcoming API but we had long discussions on this subject with the IBM people back in 2000... > Are there any Jetspeed people on this JSR? Or is it a competing viewpoint? > [much like the Log JSR suddenly wanting to turn Log4j into their > reference]. Would Jetspeed use Charon/Pluto, or would the fact that it's > an RI limit Jetspeed? > Pluto and Jetspeed would have a slightly different scope: - Pluto would be the RI for the JSR 168 API, just like Tomcat is the RI for the Servlet API - Jetspeed would a portal implementation embedding pluto, focussing on building a full-featured portal environment (with things like customization implementation, portal page definition, user preference persistence, etc...) + a set of default portlets. > I'm assuming Tomcat and JSTL had a number of Apache people in the JSR, if > this one doesn't, then it seems that it's a sourceforge concept. "We'd > like an open source RI, let's host at Jakarta, they do open-source RI's". > Is this not-invented-here-ism or maintaining scope? > My main concern at this proposal is that it only apparently covers the RI. What about the API itself ? Is it going to be open-sourced like the Servlet API ? -- Rapha�l Luta - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
