You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by ta...@jakarta.apache.org on 2004/06/14 21:48:43 UTC

[Jakarta Tapestry Wiki] Updated: PortalSupportProposal

   Date: 2004-06-14T12:48:43
   Editor: 195.56.48.202 <>
   Wiki: Jakarta Tapestry Wiki
   Page: PortalSupportProposal
   URL: http://wiki.apache.org/jakarta-tapestry/PortalSupportProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -13,3 +13,5 @@
 Access to the Servlet API is buried several layers deep, i.e., {{{getRequestCycle().getRequestContext().getRequest()}}}, and the vast majority of code and components do not access the Servlet API objects at all. A change along these lines would not be fully backwards compatible.
 
 = Discussion =
+
+The differences between the portlet and servlet API are well described at the [http://exo.sourceforge.net/bridges-intro.html eXo site]. Look at the sub-sections of the "eXo bridges and frameworks" menu item at the left menu (for example [http://exo.sourceforge.net/multiproject/exo-jsf-framework/index.html JSF portlet integration])!

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org