AW: Problem starting up new C2 beta
SOLVED IT!
My problem were older versions of compiled cocoon stuff
in the working directory of TOMCAT. -- So: Upgrading
Cocoon means you HAVE TO clean TOMCAT's working directory!
If you don't, you get very irritating error
messages, as I did.
Thanks to the people who where trying to help me on this.
Alexander
-Ursprüngliche Nachricht-
Von: Alexander Weinmann [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 7. Juni 2001 11:57
An: '[EMAIL PROTECTED]'
Betreff: AW: Problem starting up new C2 beta
I am quite sure that I don't have any
duplicate versions of avalon or other jars in the classpath.
If still think it is a general problem with the
avalon/excalibur jars included in the dist.
... Though: If others DO NOT have the problem, It
must be may local installation ...
So: Did somebody manage to start up C2beta as it comes
out of the box from the download directory?
-Ursprüngliche Nachricht-
Von: Fred Tsang [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 7. Juni 2001 11:42
An: '[EMAIL PROTECTED]'
Betreff: RE: Problem starting up new C2 beta
Hi Alexander,
take a look at the following forwarded email response from
Berin Loritsch at
Apache. If you have the same setup as me, this should do the trick:
==
Fred Tsang wrote:
Sorry,
My environment is:
Tomcat 3.2.1
JDK 1.3.1
Solaris 8
I've placed all the jar files from WEB-INF/lib into my
$TOMCAT_HOME/lib
folder, and removed any duplicates from previous
versions. I'll try
removing the avalon jars from the lib folder, but I'm a
little skeptical.
If cocoon can't find the classes, how will it operate?
thanks for the tip!
That was your whole problem! Cocoon 2 is designed to work
like servlets are
supposed to work: plug and play.
COCOON 1 TO COCOON 2 MIGRATION
Cocoon 1 forces you to place all the jars in the Tomcat lib
directory, this
was unnavoidable at the time but it was because of XSP
compilation. Cocoon
2
discovered how to be able to compile XSP without moving the
jars out of the
servlet context lib directory.
1) Remove all unnecessary/conflicting jars from $TOMCATH_HOME/lib
2) Replace $TOMCAT_HOME/lib/{xerces/parser jar} with the version of
Xerces that comes with Cocoon 2.
3) LEAVE ALL COCOON 2 JARS IN ${context}/WEB-INF/lib
cheers,
Fred
-Original Message-
From: Alexander Weinmann [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 07, 2001 9:06 AM
To: Cocoon-Users (E-Mail)
Subject: Problem starting up new C2 beta
Hello Cocooners!
I am getting back an old problem when starting up the new C2 beta
distribution:
Package Naming problems in Avalon:
In the log I have:
ERROR 1201[cocoon ] (Thread-24): Error compiling sitemap
java.lang.NoClassDefFoundError:
org/apache/avalon/logger/AbstractLoggable
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at
org.apache.avalon.excalibur.component.DefaultComponentFactory.
newInstance(De
faultComponentFactory.java:83)
at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandl
er.initialize(
ThreadSafeComponentHandler.java:78)
at
org.apache.avalon.excalibur.component.DefaultComponentSelector
.addComponent(
DefaultComponentSelector.java:306)
at
org.apache.cocoon.components.language.generator.GeneratorSelec
tor.addGenerat
or(GeneratorSelector.java:75)
at
org.apache.cocoon.components.language.generator.GeneratorSelec
tor.addGenerat
or(GeneratorSelector.java:71)
at
org.apache.cocoon.components.language.generator.GeneratorSelec
tor.select(Gen
eratorSelector.java:57)
at
org.apache.cocoon.components.language.generator.ProgramGenerat
orImpl.select(
ProgramGeneratorImpl.java:261)
at
org.apache.cocoon.components.language.generator.ProgramGenerat
orImpl.load(Pr
ogramGeneratorImpl.java:145)
at org.apache.cocoon.sitemap.Handler.run(Handler.java:224)
at java.lang.Thread.run(Thread.java:484)
I am quite sure that the class name should be
org/apache/avalon/framework/logger/AbstractLoggable
Is it sure that the Avalon and Excalibur jars included in the
dist work well
together?
abaXX
TECHNOLOGY AG
Alexander Weinmann
Development Engineer Training
[Address] Forststrasse 7,
70174 Stuttgart,
Germany
[Phone] +49-(711)-61-41-6 - 1541
[Fax] +49-(711)-61-41-6 -
[E-mail] mailto:[EMAIL PROTECTED]
[Internet] http://www.abaXX.com http://www.abaxx.com/
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Re: AW: Problem starting up new C2 beta
Quoting Alexander Weinmann [EMAIL PROTECTED]:
I am quite sure that I don't have any
duplicate versions of avalon or other jars in the classpath.
If still think it is a general problem with the
avalon/excalibur jars included in the dist.
... Though: If others DO NOT have the problem, It
must be may local installation ...
So: Did somebody manage to start up C2beta as it comes
out of the box from the download directory?
Yes, I can confirm that the C2 beta 1 is running out of the box on a NT box
with Tomcat 4 (current cvs)
Giacomo
-Ursprüngliche Nachricht-
Von: Fred Tsang [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 7. Juni 2001 11:42
An: '[EMAIL PROTECTED]'
Betreff: RE: Problem starting up new C2 beta
Hi Alexander,
take a look at the following forwarded email response from
Berin Loritsch at
Apache. If you have the same setup as me, this should do the trick:
==
Fred Tsang wrote:
Sorry,
My environment is:
Tomcat 3.2.1
JDK 1.3.1
Solaris 8
I've placed all the jar files from WEB-INF/lib into my
$TOMCAT_HOME/lib
folder, and removed any duplicates from previous versions. I'll try
removing the avalon jars from the lib folder, but I'm a
little skeptical.
If cocoon can't find the classes, how will it operate?
thanks for the tip!
That was your whole problem! Cocoon 2 is designed to work
like servlets are
supposed to work: plug and play.
COCOON 1 TO COCOON 2 MIGRATION
Cocoon 1 forces you to place all the jars in the Tomcat lib
directory, this
was unnavoidable at the time but it was because of XSP
compilation. Cocoon
2
discovered how to be able to compile XSP without moving the
jars out of the
servlet context lib directory.
1) Remove all unnecessary/conflicting jars from $TOMCATH_HOME/lib
2) Replace $TOMCAT_HOME/lib/{xerces/parser jar} with the version of
Xerces that comes with Cocoon 2.
3) LEAVE ALL COCOON 2 JARS IN ${context}/WEB-INF/lib
cheers,
Fred
-Original Message-
From: Alexander Weinmann [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 07, 2001 9:06 AM
To: Cocoon-Users (E-Mail)
Subject: Problem starting up new C2 beta
Hello Cocooners!
I am getting back an old problem when starting up the new C2 beta
distribution:
Package Naming problems in Avalon:
In the log I have:
ERROR 1201[cocoon ] (Thread-24): Error compiling sitemap
java.lang.NoClassDefFoundError:
org/apache/avalon/logger/AbstractLoggable
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at
org.apache.avalon.excalibur.component.DefaultComponentFactory.
newInstance(De
faultComponentFactory.java:83)
at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandl
er.initialize(
ThreadSafeComponentHandler.java:78)
at
org.apache.avalon.excalibur.component.DefaultComponentSelector
.addComponent(
DefaultComponentSelector.java:306)
at
org.apache.cocoon.components.language.generator.GeneratorSelec
tor.addGenerat
or(GeneratorSelector.java:75)
at
org.apache.cocoon.components.language.generator.GeneratorSelec
tor.addGenerat
or(GeneratorSelector.java:71)
at
org.apache.cocoon.components.language.generator.GeneratorSelec
tor.select(Gen
eratorSelector.java:57)
at
org.apache.cocoon.components.language.generator.ProgramGenerat
orImpl.select(
ProgramGeneratorImpl.java:261)
at
org.apache.cocoon.components.language.generator.ProgramGenerat
orImpl.load(Pr
ogramGeneratorImpl.java:145)
at org.apache.cocoon.sitemap.Handler.run(Handler.java:224)
at java.lang.Thread.run(Thread.java:484)
I am quite sure that the class name should be
org/apache/avalon/framework/logger/AbstractLoggable
Is it sure that the Avalon and Excalibur jars included in the
dist work well
together?
abaXX
TECHNOLOGY AG
Alexander Weinmann
Development Engineer Training
[Address] Forststrasse 7,
70174 Stuttgart,
Germany
[Phone] +49-(711)-61-41-6 - 1541
[Fax] +49-(711)-61-41-6 -
[E-mail] mailto:[EMAIL PROTECTED]
[Internet] http://www.abaXX.com http://www.abaxx.com/
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.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/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: Problem starting up new C2 beta
On Thu, 7 Jun 2001, Alexander Weinmann wrote: Have you left any jars in the java extension directory? Just a thought. Giacomo -Ursprüngliche Nachricht- Von: Giacomo Pati [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 7. Juni 2001 14:41 An: [EMAIL PROTECTED] Betreff: Re: AW: Problem starting up new C2 beta Quoting Alexander Weinmann [EMAIL PROTECTED]: I am quite sure that I don't have any duplicate versions of avalon or other jars in the classpath. If still think it is a general problem with the avalon/excalibur jars included in the dist. ... Though: If others DO NOT have the problem, It must be may local installation ... So: Did somebody manage to start up C2beta as it comes out of the box from the download directory? Yes, I can confirm that the C2 beta 1 is running out of the box on a NT box with Tomcat 4 (current cvs) Giacomo So it must be my installation! But I am stuck! I use Tomcat 3.2 on Windows 2000, and I am sure having removed all conflicting jars from $TOMCAT_HOME/lib. Any ideas why I still have this package naming problem, that seem to originate in an org.apache.avalon.excalibur class? -- I don't understand that. I successfully installed C2 several times from CVS But as my employee has closed the CVS port, I am forced to get the dist running ... - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.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/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
