> -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 17, 2004 9:00 AM > To: [EMAIL PROTECTED] > Subject: RE: [Portal] JSR-168 examples > > > > -----Original Message----- > > From: DURDINA Michal [mailto:[EMAIL PROTECTED] > > Sent: Monday, February 16, 2004 7:50 PM > > To: [EMAIL PROTECTED] > > Subject: [Portal] JSR-168 examples > > > > Hello, > > I am having troubles with getting JSR-168 portlet samples > > running in the portal demo. They still display "The coplet > > Portlet-1 is currently not available." in the portlet window > > and write exception in the log: > > 2004-02-16 19:39:29 WARN (2004-02-16) 19:39.29:974 > > [portal ] (/cocoon/samples/portal/portal) > > Thread-17/AbstractCopletAdapter: Unable to get content of > > coplet: Portlet-1 > > org.xml.sax.SAXException: Portlet couldn't be loaded: > > testsuite.TestPortlet1 > > > > These instructions are given in the portal demo in order to > > run JSR-168 portlet samples: > > >The Cocoon portal supports portlets conforming to the > > JSR-168. The JSR-168 contains a sample that uses the > > testsuite from the Jakarta-Pluto project. > > >These samples only work if you follow these installation > > instructions: > > > o Get the jakarta pluto project and install it into Tomcat > > (Test Pluto now). > > > o Install Cocoon as a web application in Tomcat and remove > > the Pluto webapp. > > > o Start Tomcat and run the Cocoon portal demo. You should > > now see two portlets. > > > > So I obtained last sources from jakarta-pluto project, > > started maven (rc1) fullDeployment, which installed pluto > > container into my Tomcat (4.1.27). New directories pluto and > > testsuite were created under %TOMCAT%\webapps. Pluto samples > > work when accessing http://localhost/pluto/portal. > > > > Now I am using the new release cocoon-2.1.4 running on WinXP > > platform and I configured Tomcat to deploy cocoon samples in > > %TOMCAT%\webapps\cocoon21.xml: > > <Context path="/cocoon" > > docBase="D:\cocoon-2.1.4\build\webapp\" reloadable="true" > debug="1"/> > > > > ... and they are not working. > > > > I tried to delete pluto (according to 2nd point of > > instructions) from %TOMCAT%webapps, but they are still not working. > > > > Tell me please, what am I doing wrong and why the removal of > > pluto webapplication is needed. > > > First, deleting the pluto webapp is not really needed, but it's > the webapp itself is not needed as you use Cocoon as the portal > engine. > > Now, the problem is that you didn't deploy Cocoon as a war but added > a context definition and "mounted" an external directory. > Unfortunately, > this doesn't work in Pluto, you have to deploy Cocoon into the > Tomcat webapps directory. > > Carsten >
Ok, I moved build/webapp to %TOMCAT_HOME%\webapps and renamed it to cocoon21. I started Tomcat and when typed username and password into portal demo, following messaged appeared 2 times in Tomcat log: 2004-02-18 18:35:32 ERROR (2004-02-18) 18:35.32:967 [portal ] (/cocoon21/samples/portal/auth) Thread-16/LogServiceImpl: org.apache.pluto.invoker : PortletInvokerImpl.action() - Unable to find RequestDispatcher. After click on the JSR-168 tab pane, empty boxes appeared (instead of "The coplet TestPortlet-1 is currently not available" as before) and same message appeared in the Tomcat log + 2004-02-18 18:35:52 WARN (2004-02-18) 18:35.52:669 [portal ] (/cocoon21/samples/portal/portal) Thread-16/AbstractCopletAdapter: Unable to get content of coplet: TestPortlet-1 I tried to set cocoon webapp to be crossContext by placing cocoon21.xml in the %TOMCAT_HOME%\webapps <Context path="/cocoon21" docBase="cocoon21" crossContext="true"/> but this makes things even worse and I am getting back to original exception as when cocoon weapp was mounted from outside %TOMCAT%\webapps. Is anyone else from cocoon users experiencing this problem? Thanks for help. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
