Understood, however, it appears (by reading the mail archives and the Jetspeed Resources page) that the API developed by IBM will also be adopted by Jetspeed in its next release.
Given this fact, I will re-ask my final question..."I would love to find out when the release is scheduled (approximate)?" Thanks, Jon Hamel -----Original Message----- From: Glenn Golden [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 2:42 PM To: 'Jetspeed Users List' Subject: RE: Status of the "new" Portlet API Implementation No, it does not. There is no standard yet - one product's implementation (i.e. WebSphere) does not make a standard. What does make a standard is the Portlet API process going on now under the Java Community Process. Within a year, we expect to have a real java standard for Portlet. Then, Jetspeed will support it. IBM and Sun and Jetspeed and others are part of the standards process. - Glenn -------------------------------------------- Glenn R. Golden, Systems Research Programmer University of Michigan School of Information [EMAIL PROTECTED] 734-615-1419 -------------------------------------------- > -----Original Message----- > From: Jonathan Hamel [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 03, 2002 2:27 PM > To: '[EMAIL PROTECTED]' > Subject: Status of the "new" Portlet API Implementation > > > Hello all- > > I am trying to confirm if the current release of Jetspeed > (1.3a2) supports the "standard" Portlet API developed by IBM > (i.e. the Portlet API used in WebSphere Portal Server 1.2 and > greater). > > From reading the archives and resources on the Jetspeed site, > it appears as if this has not been done yet, but I am new to > this area so I may have missed it. > > Also, if the 1.3a2 release does not support the new Portlet > API, I would love to find out when the release is scheduled > (approximate). > > Thanks in advance, > > Jon Hamel > > > > -- > To unsubscribe, e-mail: > <mailto:jetspeed-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
