Bowe, Bastian wrote:
I think it is a problem of class loading.Now I managed to show the output you normally see in your browser when loading http://localhost:8080/cocoon as a portlet! So it seems to be possible to run an Cocoon app as a JSR 168 portlet.
Anyway, clicking on a link in that portlet doesn't work. My Portlet is accessible under http://localhost:8080/pluto/portal/cocoon but e.g. the link to samples points to http://localhost:8080/pluto/portal/samples . Pointing manually to http://localhost:8080/pluto/portal/cocoon/samples is the same as http://localhost:8080/pluto/portal/cocoon . But I might find out tomorrow.
Tomorrow I will try to sum together, what I did to get so far.
Cheers
Bastian
-----Original Message-----
From: Bowe, Bastian [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 02, 2005 4:12 PM
To: 'users@cocoon.apache.org'
Subject: RE: Cocoon app as a JSR 168 portlet
Alright,
I just found the file <COCOON_HOME>/src/blocks/portal/WEB-INF/portlet.xml
and replaced my <portlet> node with the second <portlet> node from the above file. I replaced in portletentityregistry.xml the string "Cocoon" with "CocoonPortlet".
Now I'm getting a different exception:
javax.servlet.ServletException: Servlet.init() for servlet
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
After deploying Pluto and Cocoon under Tomcat you should delete portlet-api-1.0.jar and pluto-1.0.1-rc2.jar from ../cocoon/WEB-INF/lib.
These two jars should be in %TOMCAT_HOME%\shared\lib .
When you look at the portal samples (../samples/blocks/portal/portal) you will see some tips, who to run the Pluto "testsuite" portlets from the cocoon portal engine
(on the "Main" tab in the demo portal) .
gtx Gerald
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
