# The Cocoon Portal

0.1
Overview document

# The Apache Cocoon Portal

This is a demo of the Cocoon Portal Engine.

The Cocoon portal page you currently view displays some so called Coplets (= Cocoon Portlets). Each coplet displays a different content.

The different tabs display/demonstrate different aspects of the portal.

- The TabDemo1 shows a tab inside a tab, which is useful for structuring content.
- The TabDemo2 shows the same content as TabDemo2 but with just a different stylesheet for the tab.
- The Gallery tab shows some more coplets.
- The JSR-168 tab demonstrates the integration of Portlets (read more below).

THIS IS A SAMPLE PORTAL!

It demonstrates several features of the portal engine, so it's not optimized for production. Make sure that if you use the portal for your own projects that you remove all unused stuff from the configuration! Every configured feature might have an impact on the performance.

For more information visit the Cocoon Homepage.

# The JSR 168

The Cocoon portal supports portlets conforming to the JSR 168. The JSR 168 tab contains a sample using the testsuite from the Pluto project.

These samples only work if you follow these installation instructions:

- Get the Pluto project and install it into Tomcat (Test Pluto now).
- Install Cocoon as a web application in Tomcat and remove the Pluto webapp. Please note, that it is currently not possible to start Cocoon directly from a war file; it has to be expanded.
- Remove the pluto-*.jar and the portlet-api-*.jar from the Cocoon WEB-INF/lib directory.
- Start Tomcat and run the Cocoon portal demo. You should now see two portlets.

The current implementation searches for portlets in all directories that are next to the Cocoon webapp directory. So, if you put Cocoon into the webapps directory of Tomcat, you should put your portlets there as well.