The PortletBridge Portlet is a JSR 168 compliant portlet that allows a downstream web site to be proxied as a portlet. By default it only displays the content of the BODY but custom XSLT can be used to transform the data from the downstream site.
There are several differences between using an IFrame and the PortletBridge Portlet. Probably the biggest advantage to using an IFrame is that it is simpler than the PortletBridge Portlet and the downstream site will often be more faithfully rendered. There are however several advantages to using the PortletBridge Portlet.
Copy the portlet war into the %JBOSS_HOME%/server/default/deploy directory
NOTE: If you're deploying into Liferay on top of JBoss, you will have to remove the commons-logging jar from the portletbridge-portlet.war file to make it work.
In order to deploy into Gridsphere you will need to:
<servlet> <servlet-name>PortletServlet</servlet-name> <servlet-class>org.gridlab.gridsphere.provider.portlet.jsr.PortletServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>PortletServlet</servlet-name> <url-pattern>/jsr/portletbridge-portlet</url-pattern> </servlet-mapping>
14:04:45,295 ERROR [org.apache.catalina.session.ManagerBase] Exception loading s essions from persistent storage java.io.InvalidClassException: org.portletbridge.portlet.DefaultBridgeRequest; l ocal class incompatible: stream classdesc serialVersionUID = -785819319195243178 6, local class serialVersionUID = 4504756989609725196