Michael Sallman wrote:
>
> On Sun, 19 Mar 2000, Michael Sallman wrote:
>
>
> I found in logs/tomcat.log that cocoon.jar is missing
> org.apache.cocoon.producer.ProducerFromMap.
> While I was waiting for Cocoon to download, I copied Cocoon-1.6.jar back
> into /lib. In JetSpeedResources.properties in the Portlet Markup section
> I changed /content/xml/... to /opt/tomcat/webapps/content/xml/...
> and voila, I have the Jetspeed Logon screen!!!!
>
See below, how I got everything working for last friday CVS image...
> Now the new problem. When I log in, I get the error:
> java.io.FileNot Found Exception:
> http://localhost:8080/opt/tomcat/webapps/xml/defaultPortlets.xml
>
> If I change back to /content/xml/*, no Logon screen and I get the error
> java.lang.ExceptionInInitializerError:
> java.util.NoSuchElementException:
> contentfeeds.portletbrowser.maxportlets doesn't map to an existing object.
>
contentfeeds.portletbrowser.maxportlets should be defined in the
JetspeedResources.properties file. it is used by the PortletBrowserPortlet.
Warning: when I launch the PortletBrowserPortlet I get a OutOfMemory exception
even though I have ample RAM on my desktop, I would recommend disabling
the call to this portlet in defaultPortlets.xml for the moment.
The issue with the blank logon screen is that in JetspeedResources
portletmarkup.default
and
portletmarkup.all
are assumed to be URL, the default values of /content/xml/... they are
assumed to be HTTP URL, ie Jetspeed query http://localhost/content/xml/...
Now, if you have setup Cocoon on your web server to handle *.xml files,
the result of the query to http://localhost/content/xml/... will first be
handled by Cocoon, which won't find any processing instruction inside but
format the result as HTML (default formatter) which will cause a SAX Handling
exception when Jetspeed tries to read it, thus a blank screen.
Solution:
- put in the JetspedResources
portletmarkup.default=file:///mypath/to/content/xml/...
portletmarkup.all=file:///mypath/to/content/xml/...
(or desactivate Cocoon on this instance of the web server)
- clear manually the cache directory defined in cache.directory
(I've got some trouble with this Jetspeed version to get it to refresh the
cache)
- restart your servlet engine
- pray :)
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
