Return-Path: Delivered-To: apmail-jakarta-jetspeed-dev-archive@apache.org Received: (qmail 19862 invoked from network); 1 May 2002 17:37:51 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 May 2002 17:37:51 -0000 Received: (qmail 20492 invoked by uid 97); 1 May 2002 17:37:52 -0000 Delivered-To: qmlist-jakarta-archive-jetspeed-dev@nagoya.betaversion.org Received: (qmail 20420 invoked by alias); 1 May 2002 17:37:51 -0000 Delivered-To: jakarta-archive-jetspeed-dev@jakarta.apache.org Received: (qmail 20379 invoked by uid 97); 1 May 2002 17:37:51 -0000 Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jetspeed Developers List" Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@jakarta.apache.org Received: (qmail 20311 invoked by uid 98); 1 May 2002 17:37:50 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3AF04479.3060200@networks.groupvu.com> Date: Wed, 02 May 2001 19:31:37 +0200 From: raphael.luta@networks.groupvu.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 X-Accept-Language: fr, en MIME-Version: 1.0 To: Jetspeed Developers List Subject: Re: Connection between JSR 168, JetSpeed and IBM? References: <019301c1f11a$ccc9b760$84e5c53f@MOZART> <009301c1f131$d9423190$1335fea9@peak> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Endre Stolsvik wrote: >| There Portlet API JSR 168 Expert Group was founded in February this >| year. It will be defining: >| >| 1. Portlet API Standard >| 2. Portlet API Reference Implementation >| 3. Portlet API TCK >| >| IBM and Sun are co-spec leads. >| IBM's original portlet API proposal has had some influence on the >| Portlet API standard. >| However the new standard is being designed by the Expert Group, not by >| IBM alone. > >All this is said in the JSR 168 spec. I browsed the jetspeed archives, and I >got some more information there, like that the JSR 162 and JSR 167, made by >IBM and SUN respectively, both got dropped 20. January. Sun and IBM began a >joint effort, the JSR 168, the 12. February. And Apache is in the Expert >Group of this spec. > > I'm pretty sure that since David is involved in the JSR 168 he cannot elaborate on what is being said within this group because of a NDA... >That "propsed Portlet API" laying in the jetspeed CVS, where did that come >from? It's seems to be written by three german IBM'ers.. Are they active >JetSpeed developers? I'm asking since they are using the >org.apache.jetspeed.portlet packages in the Portlet Development Guide for >WebSphere Portal 4.1 (The link I pasted). That piece of software is >apparently due to be released 31. May.. And in that guide, they state the >following: > "The Portlet API offered in WebSphere Portal Version 4.1 is the first step >toward the Portlet API standardization. For more information about the >portlet specification..." > >I was just wondering if anyone had some more "history" behind this stuff.. > > > Easiest way to get an "historical perspective" on this subject is to browse the Jetspeed mailing-list archives from October 2000 to March 2001, you should get most of the conversations that occurred about this API. (look mainly for the Portlet API thread...) -- Rapha�l Luta - raphael.luta@networks.groupvu.com Professional Services Manager Vivendi Universal Networks - Paris -- To unsubscribe, e-mail: For additional commands, e-mail: