RE: Version Hell

2002-06-13 Thread Vadim Gritsenko 

Please send plain text emails. My responses start with ---

-Original Message-
From: daniel robinson [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, June 13, 2002 7:20 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Version Hell

Perry,

Thanks.  I just double checked the 2.0.2 distro and it is NOT in the war
file. 


--- Cocoon 2.0.2 comes with Pizza Java compiler which is smaller and
faster then Sun's Javac (you can search
http://xml.apache.org/cocoon/changes.html to see this). Instead of
reference to the Javac, Pizza should be referenced in the cocoon.xconf.
It is so (IIRC) in the binary distribution, and it is added
automagically to the cocoon.xconf when you build source distribution
*and* pizza jar is in the lib/optional.



 Hmmm.  I put it back and now that error is gone.  I'm back dealing with
the problem I had previous to this:

java.lang.RuntimeException: Stylesheet directed termination
    at
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:32
31)

which I've been led to believe is a result of a badly formed sitemap
file.  Of 


--- Cocoon 2.0.2 checks syntax of your sitemap file and refuses it to
compile if finds something. Cocoon 2.0 does not have this feature. To
find out the error, please open log files and search for error text, it
is logged with exception above "java.lang.RuntimeException: Stylesheet
directed termination" exception.


Vadim




course this is exactly the same file I was using with 2.0.0 just fine.
 And it doesn't seem that there are any XML errors in it (I checked it
with an XML aware tool).  Ok.  Whatever.

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]>

Re: Version Hell

2002-06-13 Thread daniel robinson 



Perry,

Thanks.  I just double checked the 2.0.2 distro and it is NOT in the war
file.  Hmmm.  I put it back and now that error is gone.  I'm back dealing
with the problem I had previous to this:

java.lang.RuntimeException: Stylesheet directed termination
    at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3231)

which I've been led to believe is a result of a badly formed sitemap file.
 Of course this is exactly the same file I was using with 2.0.0 just fine.
 And it doesn't seem that there are any XML errors in it (I checked it with
an XML aware tool).  Ok.  Whatever.

Dan


Faulkner, Perry wrote:
[EMAIL PROTECTED]">
  
  
Hi  Daniel,
   
  
javac.jar is a copy of tools.jar from the JDK, renamed and included,  normally, in
the cocoon.war file by the build procedure for source  distro or included
as standard with the binary distro. I don't know why  it's missing in your
configuration, but copy/rename and put into classpath may  solve your problem!
   
  
It  would explain some of your other problems, as it would need the java
compiler  from it, to rebuild your sitemap after any changes had been  detected.
   
  
Perry
  

-Original Message-
From: daniel robinson[mailto:[EMAIL PROTECTED]]
Sent: Friday, 14 June 2002 8:25
To:    [EMAIL PROTECTED]
Subject: Re: VersionHell


I thought it might have to do with the reload method,but it didn't seem
reasonable that it would pop an error until the sitemap wasre-built.
 So that fixes that problem.  

Anybody with ideasfor:

java.lang.RuntimeException: No compiler found in your classpath.Make
sure you added 'tools.jar'
    atorg.apache.cocoon.components.language.programming.java.Javac.(Javac.java:91)


?

Thanks


DarrellCumming wrote:
[EMAIL PROTECTED]" type="cite">
  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=2He states that the _DEFAULT_ asynchron reload-method is broken and will beremoved from > 2.03. Good luck.Darrell
  
-Original Message-From: daniel robinson [mailto:[EMAIL PROTECTED]] Sent: June 13, 2002 3:06 PMTo: [EMAIL PROTECTED]Subject: Re: Version HellOh, 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 ofmigrating 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 beeasier and I had had trouble with 4.0.3)It is working fine, so I installed c 2.0.2It 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 befine 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\sitemap_xmap.java:3088) 
  
   at org.apache.

RE: Version Hell

2002-06-13 Thread Faulkner, Perry 



Hi 
Daniel,
 
javac.jar is a copy of tools.jar from the JDK, renamed and included, 
normally, in the cocoon.war file by the build procedure for source 
distro or included as standard with the binary distro. I don't know why 
it's missing in your configuration, but copy/rename and put into classpath may 
solve your problem!
 
It 
would explain some of your other problems, as it would need the java compiler 
from it, to rebuild your sitemap after any changes had been 
detected.
 
Perry

  -Original Message-From: daniel robinson 
  [mailto:[EMAIL PROTECTED]]Sent: Friday, 14 June 2002 8:25To: 
  [EMAIL PROTECTED]Subject: Re: Version 
  HellI thought it might have to do with the reload method, 
  but it didn't seem reasonable that it would pop an error until the sitemap was 
  re-built.  So that fixes that problem.  Anybody with ideas 
  for: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)?ThanksDarrell 
  Cumming wrote:
  [EMAIL PROTECTED] 
  type="cite">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=2He states that the _DEFAULT_ asynchron reload-method is broken and will beremoved from > 2.03. Good luck.Darrell
-Original Message-From: daniel robinson [mailto:[EMAIL PROTECTED]] Sent: June 13, 2002 3:06 PMTo: [EMAIL PROTECTED]Subject: Re: Version HellOh, 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 ofmigrating 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 beeasier and I had had trouble with 4.0.3)It is working fine, so I installed c 2.0.2It 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 befine 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   atorg.apache.cocoon.www.sitemap_xmap.process(D:\Programs\Tomcat4\work\DEFAULT\cocoon\cocoon-files\org/apache/cocoon/www\sitemap_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. 
  To unsubscribe, e-mail: <[EMAIL PROTECTED]>
  For additional commands, e-mail:   <[EMAIL PROTECTED]>
  -Please check that your question  has not already been answered in theFAQ before posting. To unsubscribe, e-mail: <[EMAIL PROTECTED]>For additional commands, e-mail:   <[EMAIL PROTECTED]>-Please check that your question  has not already been answered in theFAQ before posting. To unsubscribe, e-mail: <[EMAIL PROTECTED]>For additional commands, e-mail:

Re: Version Hell

2002-06-13 Thread daniel robinson 



I thought it might have to do with the reload method, but it didn't seem
reasonable that it would pop an error until the sitemap was re-built.  So
that fixes that problem.  

Anybody with ideas for:

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)


?

Thanks


Darrell Cumming wrote:
[EMAIL PROTECTED]">
  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=2He states that the _DEFAULT_ asynchron reload-method is broken and will beremoved from > 2.03. Good luck.Darrell
  
-Original Message-From: daniel robinson [mailto:[EMAIL PROTECTED]] Sent: June 13, 2002 3:06 PMTo: [EMAIL PROTECTED]Subject: Re: Version HellOh, 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 ofmigrating 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 beeasier and I had had trouble with 4.0.3)It is working fine, so I installed c 2.0.2It 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 befine 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\sitemap_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. 
  
  
  
To 

unsubscribe, e-mail: <[EMAIL PROTECTED]>

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


-Please check that your question  has not already been answered in theFAQ before posting. To unsubscribe, e-mail: <[EMAIL PROTECTED]>For additional commands, e-mail:   <[EMAIL PROTECTED]>

-Please check that your question  has not already been answered in theFAQ before posting. To unsubscribe, e-mail: <[EMAIL PROTECTED]>For additional commands, e-mail:   <[EMAIL PROTECTED]>

RE: Version Hell

2002-06-13 Thread Darrell Cumming 

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]>

Re: Version Hell

2002-06-13 Thread daniel robinson 

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\sitemap_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. 
>
> 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. 

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