I noticed a few things (these are from Saturday, in the release_1_3a1-branch)
 
1)  when the JetspeedConfig.jcfg file gets written out, the end-of-line markers get changed. On my system, it makes the file appear to be one long line, so it's hard to edit after that.
2) in top_default.jsp, I had to change the taglib line
from:
      <%@ taglib uri='WEB-INF/templates/tld/template.tld' prefix='jetspeed' %>
to:
      <%@ taglib uri='../tld/template.tld' prefix='jetspeed' %> 
 

3) I'm not sure of the state of the profiler, which is correct? (The second one works, but the distribution has files of the first form)
 
  C:\TOMCAT\WEBAPPS\jetspeed/WEB-INF/psml/demo/homeHTML.psml
or:
  C:\TOMCAT\WEBAPPS\jetspeed\WEB-INF\psml\user\userid\html\default.psml
 
 
4) I am seeing this stack trace during startup (for many local file references, not just jetspeed-config.jcfg). But everything still works fine.

[Sat Dec 16 13:57:14 EST 2000] --  ERROR  --
 Exception:  java.net.MalformedURLException: no protocol: jetspeed-config.jcfg
 Stack Trace follows:
 java.net.MalformedURLException: no protocol: jetspeed-config.jcfg
 at java.net.URL.<init>(Unknown Source)
 at java.net.URL.<init>(Unknown Source)
 at java.net.URL.<init>(Unknown Source)
 at org.apache.jetspeed.services.urlmanager.URLFetcher.refresh(URLFetcher.java:220)
 at org.apache.jetspeed.daemon.impl.util.diskcachedaemon.URLRefresher.run(URLRefresher.java:105)
 at org.apache.jetspeed.services.threadpool.RunnableThread.run(RunnableThread.java:145)
 
Carol

Reply via email to