The IFramePortlet is definitely the route to go when bringing in pages from an existing web application that has navigation - like a search screen from another app that posts search criteria and gets back some data. I am certainly no expert, but I got it working.
One thing to watch out for, is that you need to create a source parameter that has the url of your starting page, and not the URL parameter which you would have been using - the Javadocs describe how to set it up pretty well but the admin pages still show the URL parameter. Doing a file compare between the 2 java classes (WebPagePortlet), there are some differences, but I was unable to determine from comments any reasoning for those differences. Others probably know why the changes and for what reasons. I just use the WebPagePortlet2 one, sounds newer <g>. Jason Trust -----Original Message----- From: Stefano Bianchi [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 11:29 AM To: Jetspeed Users List Subject: WebPagePortlet vs IFramePortlet Hi, could anyone provide me with a simple explanation about differences between WebPagePortlets and IFramePortlet? And between WebPagePortlet1 and WebPagePortlet2? I'm developing a portal in which I embed different webapps into Jetspeed, that actually acts like a "webapps" container. I think IFramePortlet is the only one that allows internal navigation within a Jetspeed page. Am I right? Thank you for your attention & time Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
