t; information?
>
> Thanks!
> Ted
>
>
> -Original Message-
> From: java guru [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, August 19, 2001 5:20 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Dreaded: Sitemap handler's sitemap is
> not available
>
>
&g
]
Subject: Re: Dreaded: Sitemap handler's sitemap is not available
Hi.,
I hate to say "search the mail archive" but here is
simple explanation...
1. Sitemap is one BIG java program to be compiled on
c2 startup...
2. Any problem resulting from sitemap compilation
could result in si
b.xml file, but I was unsure what to put there. Can you offer an
additional suggestion?
Thanks for your time!
Ted
-Original Message-
From: Liam Morley [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 19, 2001 6:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Dreaded: Sitemap handler's site
I found it necessary to include more jar files. Specifically, ALL the jar
files :o) For example, I'm pretty sure the avalon jars get used, so that
might be part of it. Also I think that when I built there was a difference
in the files size between the cocoon.jar that came with installation and
the
Dear Ted and all the rest,
This is exactly what happened to me when I tried to install Cocoon2 b2.
In my case, I have already installed Cocoon2 b1 without a problem, and it
happened when I tried to move to beta 2 maintaining exactly the same
configuration (Windows2K, Tomcat 3.2.3, Sun JDK 1.3.1
Hi.,
I hate to say "search the mail archive" but here is
simple explanation...
1. Sitemap is one BIG java program to be compiled on
c2 startup...
2. Any problem resulting from sitemap compilation
could result in sitemap being NOT compiled and hence
"component for hint: sitemap not found"..
3.
