Raphael Lute: thank you very much for your tremendously helpful and informative answers!
So.. While reading the document for the IBM WebSphere Portal v.4.1, I run into something that I do not understand, and thought that maybe you (or someone else here) may be able to answer: On page 7, a Porlet is shown like an extension of PortletAdapter, which is an extension of Portlet. I guess the latter one is meant to shown "implements". Nevertheless, these are both from package org.apache.jetspeed.portlet. OK. But what I do not understand, is the logic with the next step, where Porlet inherits from _javax.servlet.http.HttpServlet_. Has the Jetspeed API, old or new, _ever_ had any inheritance from the servlet specification? Is the Jetspeed API shown in this document actually available from the Jetspeed CVS? This inheritance scares me! This, to me, seems like a TOTAL trashing of the concept of a "loadable module" or "portal application" that I've found it called here at Jetspeed. You're supposed to package the portal application in a .war file. How are you supposed to have multiple portal applications installed, then? Install multiple _web_ applications? But how is the communication between the different portal applications supposed to be made? For example, a HttpSession should not be migrated between different web applications, according to the Servlet specs. Given that IBM somewhat ambiguously states "The Portlet API offered in WebSphere Portal Version 4.1 is the first step toward the Portlet API standardization." (pg 6), I wonder about this Servlet dependency. Jason van Zyl and David Sean Taylor: hi! Do you folks have any inside info you can share?! ;) Thanks, Endre. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
