You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Lewis, Andrew J" <An...@jbosc.ksc.nasa.gov> on 2002/01/24 21:54:48 UTC
Excalibur hasComponent question....
I saw a patch related to this on Jan 18th and just wanted to see if there
was anymore info and get an opinion on wether this sounds like the same
problem. I'm running NT4.0, Sun JDK 1.3.1, Tomcat 3.3, and Cocoon 2 from CVS
HEAD. Everything builds fine, but when accessing it I get:
org.apache.cocoon.ProcessingException: The sitemap handler's sitemap is not
available. Please check logs for the exact error.
The sitemap.log contains the following:
EBUG (2002-01-24) 15:09.06:764 [sitemap] (/cocoon/) Thread-16/Handler:
Beginning sitemap regeneration
DEBUG (2002-01-24) 15:09.06:944 [sitemap] (/cocoon/)
Thread-16/DefaultRoleManager: looking up shorthand , returning null
DEBUG (2002-01-24) 15:09.06:964 [sitemap] (/cocoon/)
Thread-16/DefaultRoleManager: looking up shorthand , returning null
DEBUG (2002-01-24) 15:09.06:964 [sitemap] (/cocoon/)
Thread-16/DefaultRoleManager: looking up shorthand , returning null
DEBUG (2002-01-24) 15:09.06:964 [sitemap] (/cocoon/)
Thread-16/DefaultRoleManager: looking up shorthand , returning null
DEBUG (2002-01-24) 15:09.06:974 [sitemap] (/cocoon/)
Thread-16/DefaultRoleManager: looking up shorthand , returning null
DEBUG (2002-01-24) 15:09.06:974 [sitemap] (/cocoon/)
Thread-16/DefaultRoleManager: looking up shorthand , returning null
DEBUG (2002-01-24) 15:09.06:974 [sitemap] (/cocoon/)
Thread-16/DefaultRoleManager: looking up shorthand , returning null
ERROR (2002-01-24) 15:09.06:974 [sitemap] (/cocoon/) Thread-16/Handler:
Error compiling sitemap
java.lang.NoSuchFieldError: manager
at
org.apache.cocoon.www.sitemap_xmap.configure(sitemap_xmap.java:173)
at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(De
faultComponentFactory.java:172)
at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(
ThreadSafeComponentHandler.java:84)
at
org.apache.cocoon.components.language.generator.GeneratorSelector.addGenerat
or(GeneratorSelector.java:135)
at
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.addComp
iledComponent(ProgramGeneratorImpl.java:355)
at
org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(Pr
ogramGeneratorImpl.java:189)
at org.apache.cocoon.sitemap.Handler.run(Handler.java:228)
at java.lang.Thread.run(Thread.java:484)
Does this look to anyone else like the same problem, and if so, has anyone
any comments on the patch from Vadim Gritsenko on Jan 18?
Thanks...
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: Excalibur hasComponent question....
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Lewis, Andrew J [mailto:Andrew.Lewis@jbosc.ksc.nasa.gov]
>
>
> I saw a patch related to this on Jan 18th and just wanted to see if
there
> was anymore info and get an opinion on wether this sounds like the
same
> problem. I'm running NT4.0, Sun JDK 1.3.1, Tomcat 3.3, and Cocoon 2
from CVS
> HEAD. Everything builds fine, but when accessing it I get:
>
> org.apache.cocoon.ProcessingException: The sitemap handler's sitemap
is not
> available. Please check logs for the exact error.
>
> The sitemap.log contains the following:
<snip reason="don't have comments"/>
> ERROR (2002-01-24) 15:09.06:974 [sitemap] (/cocoon/)
Thread-16/Handler:
> Error compiling sitemap
> java.lang.NoSuchFieldError: manager
> at
> org.apache.cocoon.www.sitemap_xmap.configure(sitemap_xmap.java:173)
> at
This looks like you have an old sitemap_xmap.class - from the previous
Cocoon version. Make sure there is no any stale *_xmap.class-es in your
working directories.
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org