RE: The sitemap handler's sitemap is not available

2001-06-20 Thread Guangzu Wang (Houston)

Thanks to Java Guru, Matthieu VIDAL, Daniel Pfuhl for your prompt reply and
great help. Also thanks Eirik Dentz for your research on display svg
although I don't understand all and I have RH Linux instead of Debian, you
also pointed to me a great archive site which I have been tried to search
for a while.

Yeap, the problem is because of display variable related to svg and I
started it from X Windows (with linux console) and that solved the problem.
Although I still get some warning about the font-properties, blah, blah.

The next step is figure out how to make it work from the remote console and
that's the Eirik's research all about, right? :) I need to do that since our
server room is so uncomfortable :(

Thanks for you guys again for making my first Cocoon experience enjoyable.

Guangzu
-Original Message-
From: java guru [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 8:08 AM
To: [EMAIL PROTECTED]
Subject: Re: The sitemap handler's sitemap is not available


I am not sure if this solves your problem... You have
posted the log from the point where it said sitemap
handler not found...I am also newbie..but what i
observed is that when u start the
cocoon(http://localhost:8080/cocoon) it first try to
compile the sitemap...ANY SITEMAP COMPILE ERRORS would
results in subsequent sitemap handler not found
errors. So I alwasy look beyond the sitemap not found
error in the log to see if there were any prior
errors after the cocoon started(i delete the log
before starting cocoon so that what i have in log
after start is fresh)...

For example when i run cocoon on my redhat linux thru
command line the sitemap couldnt get compiled resulted
in sitemap handler not found..but when i look at the
log from the beginning..i see this svg stuff
error..java swing related ( not be able to connect to
display 0.0) error which in turn resulted in sitemap
not being compiled... then i started the server from
gui environment and everything worked fine

Hope this helps..


--- Guangzu Wang (Houston)
[EMAIL PROTECTED] wrote:  Hi all,
 
 I installed Tomcat 3.2.2 and Cocoon2, the Tomcat
 works well
 (http://localhost:8080) but Cocoon2 not, it gave me
 the error message of
 The sitemap handler's sitemap is not available. I
 did delete jaxp.jar and
 copied xerces-1.4.0.jar and changed parser.jar to
 zparser.jar as suggested.
 When I search the archive list, I found similar
 problem and suggestions was
 use Tomcat 4. So I installed Tomcat 4.0 beta 5.
 Again I changed the class
 path in web.xml which make servlet.jar visible to
 Cocoon2 in web.xml before
 building cocoon.war. After I run the Tomcat and
 Cocoon, I still got similar
 error message of The sitemap handler's sitemap is
 not available.  My Linux
 box is Red Hat 7.1 and I installed JDK 1.3.1 and
 setup the JAVA_HOME and
 path accordingly.
 
 I actually need a server side xslt process tool. I
 tried AxKit since most of
 my code is perl but unfortunately I can not get
 Sablotron for I can not get
 http://www.gingerall.com/ for some reasons(host
 down?). Then I turn to
 Cocoon2. Look like this is not a easy task either.
 
 Anybody get a clue, Thanks a million in advance!
 
 Guangzu
 
 Here's error message from Tomcat 3.2.2 and Tomcat
 4.0 beta 5.
 
 Tomcat 3.2.2
 
 org.apache.cocoon.ProcessingException: The sitemap
 handler's sitemap is not
 available.
  at

org.apache.cocoon.sitemap.Manager.setupProcessing(Manager.java:178)
  at

org.apache.cocoon.sitemap.Manager.invoke(Manager.java:95)
  at
 org.apache.cocoon.Cocoon.process(Cocoon.java:328)
  at

org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:488)
  at

javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
  at

org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.
java:405)
  at

org.apache.tomcat.core.Handler.service(Handler.java:287)
  at

org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
  at

org.apache.tomcat.core.ContextManager.internalService(ContextMa
nager.java:79
 7)
  at

org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
  at

org.apache.tomcat.service.http.HttpConnectionHandler.processCon
nection(HttpC
 onnectionHandler.java:213)
  at

org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint
.java:416)
  at

org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPoo
l.java:501)
  at java.lang.Thread.run(Thread.java:484)
 
 Tomcat 4.0 beta 5.
 
 org.apache.cocoon.ProcessingException: The sitemap
 handler's sitemap is not
 available.
  at

org.apache.cocoon.sitemap.Manager.setupProcessing(Manager.java:178)
  at

org.apache.cocoon.sitemap.Manager.invoke(Manager.java:95)
  at
 org.apache.cocoon.Cocoon.process(Cocoon.java:328)
  at

org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:488)
  at

javax.servlet.http.HttpServlet.service(HttpServlet.java:853

RE: The sitemap handler's sitemap is not available

2001-06-20 Thread Guangzu Wang (Houston)

After I read Eirik Dentz email in the archive
(http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=99187677417717w=2)
again, I checked my Linux box and found a Xvfb server (XFree86-Xvfb) is
already installed and running. So I set up the DISPLAY by:
shell$ export DISPLAY=:0
and I run Tomcat 4.0 b5 with C2 from my comfortable remote desk, bingo!
Cheers!

Guangzu

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




The sitemap handler's sitemap is not available

2001-06-19 Thread Guangzu Wang (Houston)

Hi all,

I installed Tomcat 3.2.2 and Cocoon2, the Tomcat works well
(http://localhost:8080) but Cocoon2 not, it gave me the error message of
The sitemap handler's sitemap is not available. I did delete jaxp.jar and
copied xerces-1.4.0.jar and changed parser.jar to zparser.jar as suggested.
When I search the archive list, I found similar problem and suggestions was
use Tomcat 4. So I installed Tomcat 4.0 beta 5. Again I changed the class
path in web.xml which make servlet.jar visible to Cocoon2 in web.xml before
building cocoon.war. After I run the Tomcat and Cocoon, I still got similar
error message of The sitemap handler's sitemap is not available.  My Linux
box is Red Hat 7.1 and I installed JDK 1.3.1 and setup the JAVA_HOME and
path accordingly.

I actually need a server side xslt process tool. I tried AxKit since most of
my code is perl but unfortunately I can not get Sablotron for I can not get
http://www.gingerall.com/ for some reasons(host down?). Then I turn to
Cocoon2. Look like this is not a easy task either.

Anybody get a clue, Thanks a million in advance!

Guangzu

Here's error message from Tomcat 3.2.2 and Tomcat 4.0 beta 5.

Tomcat 3.2.2

org.apache.cocoon.ProcessingException: The sitemap handler's sitemap is not
available.
at
org.apache.cocoon.sitemap.Manager.setupProcessing(Manager.java:178)
at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:95)
at org.apache.cocoon.Cocoon.process(Cocoon.java:328)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:488)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79
7)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:213)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Thread.java:484)

Tomcat 4.0 beta 5.

org.apache.cocoon.ProcessingException: The sitemap handler's sitemap is not
available.
at
org.apache.cocoon.sitemap.Manager.setupProcessing(Manager.java:178)
at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:95)
at org.apache.cocoon.Cocoon.process(Cocoon.java:328)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:488)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:254)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:194)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:255)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:225)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2252)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164
)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:446)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:163)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
875)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:952)
at java.lang.Thread.run(Thread.java:484)