Have a look at your $COCOON_DIR/WEB-INF/cocoon.xconf 

Under the sitemap section. :)

It explains something like this;


    The reload-method specifies the method for the regeneration:
    asynchron: If the sitemap changes, the sitemap is regenerated at the
               next request in the background and the incoming request is
               served with the old sitemap. All subsequent requests are
               served with the old sitemap until the regeneration in the
               background has finished.
    synchron: If the sitemap changes, the sitemap is regenerated at the
              next request. When the regeneration is finished, the request
              (and all subsequent ones) is served with the new sitemap.



So set the reload-method to syncron and your problem will go away.

FYI: I searched the archives and found this response from Vadim Gritsenko 

http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=102379851819365&w=2

He states that the _DEFAULT_ asynchron reload-method is broken and will be
removed from > 2.03. 

Good luck.


Darrell

> -----Original Message-----
> From: daniel robinson [mailto:[EMAIL PROTECTED]] 
> Sent: June 13, 2002 3:06 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Version Hell
> 
> 
> Oh, one more thing.  The error reported when I go to the Cocoon page 
> stops occurring after a minute or two.  In other words, make 
> a change in 
> the sitemap, save, get error, wait a minute, error all gone. (repeat 
> process because you think you've done something wrong).  What 
> is THAT about?
> 
> daniel robinson wrote:
> 
> > I was running fine under Tomcat 4.0.3 and Cocoon 2.0.0.  As part of
> > migrating to an ISP I needed to switch to c 2.0.2.  so:
> >
> > I downgraded to Tomcat 3.3.1 (because the install was going to be
> > easier and I had had trouble with 4.0.3)
> > It is working fine, so I installed c 2.0.2
> > It was ok so I installed my app (I placed the 2.0.2 libs in my lib 
> > directory and then created a WAR)
> > I got this error:
> >
> > java.lang.RuntimeException: No compiler found in your 
> classpath. Make
> > sure you added 'tools.jar'
> >    at 
> > 
> org.apache.cocoon.components.language.programming.java.Javac.(
> Javac.java:91) 
> >
> >
> > I couldn't figure out what was going on as my classpath seems to be
> > fine and I haven't changed ANYTHING in my system while I was doing 
> > this upgrade, I though it might be some problem with 
> environment space 
> > (Windows98) so I tried to force the cocoon installation to 
> compile the 
> > sitemap.  I put a couple of spaces in that file (in an inoffensive 
> > location) and now cocoon reports:
> >
> > java.lang.NullPointerException
> >    at
> > 
> org.apache.cocoon.www.sitemap_xmap.process(D:\Programs\Tomcat4
> \work\DEFAULT\cocoon\cocoon-files\org/apache/cocoon/www\sitema
> p_xmap.java:3088) 
> >
> >    at org.apache.cocoon.sitemap.Handler.process(Handler.java:222)
> >
> >
> > When I restarted Tomcat this error went away, but came 
> right back when
> > I edited the sitemap file.
> >
> > I'm lost.
> >
> > Dan
> >
> >
> >
> > 
> ---------------------------------------------------------------------
> > Please check that your question  has not already been 
> answered in the
> > FAQ before posting.     
> <http://xml.apache.org/cocoon/faq/index.html>
> >
> > To 
> unsubscribe, e-mail:     <[EMAIL PROTECTED]>
> > For additional commands, e-mail:   
> <[EMAIL PROTECTED]>
> >
> >
> >
> 
> 
> 
> ---------------------------------------------------------------------
> Please check that your question  has not already been answered in the
> FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>
> 
> To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>
> 

---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to