>
> Built it from CVS. Removed the old deployment, and cleared out the
> Tomcat work directory. Deployed the new WAR. The FileManager is still
> reporting a NULL, and then a huge NullPointerException stack trace came
> up on the default page.
>
> Not sure what else to do.
>
Mmmh.. looking at
Success!
Turns out I had previously checked out the CVS using the Porlet API tag.
When I checked it out again, CVS very politely remembered that, so I
didn't get the current HEAD. Did a clean check-out, build, and deploy,
and a2-dev is working as expected.
-T.
Paul Spencer wrote:
>
> Ted,
> D
Ted,
Do any portlets on the homepage appear?
You can remove offending portlets by edit
jetspeed\WEB-INF\psml\anon\html\en\default.psml. The problem may be
limited to specific portlet types, i.e. RSS.
I am not sure what the problem is. I am running Tomcat v3.3-b1 and have
no experience with Tom
Paul Spencer wrote:
>
> Ted,
> The e-mail problem has been fixed in the Jetspeed 1.3a2-dev, a.k.a. CVS.
>
> Paul Spencer
Thanks, Paul.
Built it from CVS. Removed the old deployment, and cleared out the
Tomcat work directory. Deployed the new WAR. The FileManager is still
reporting a NULL, and
Ted,
The e-mail problem has been fixed in the Jetspeed 1.3a2-dev, a.k.a. CVS.
Paul Spencer
Ted Husted wrote:
>
> NT Workstation 4 sp6
> Tomcat 4.0b7 binary
> Jetspeed 1.3a1 binary
>
> After installing the WAR, Tomcat complains
>
> DCE: isLocal:
>
>url=file:///D:\public\tomcat4\webapps\jetspe
NT Workstation 4 sp6
Tomcat 4.0b7 binary
Jetspeed 1.3a1 binary
After installing the WAR, Tomcat complains
DCE: isLocal:
url=file:///D:\public\tomcat4\webapps\jetspeed\WEB-INF\cache\http_www.apacheweek.com_issues_apacheweek-headlines.xml
file=
D:\public\tomcat4\webapps\jetspeed\WEB-INF\cache\ht
