It means that something is not correct with the way Apache SOAP has been
installed on the server. If you did not download a nightly build or the CVS
sources, you may have followed instructions that applied to Tomcat 3.2
rather than 4.0. The current instructions for 4.0 are at
http://cvs.apache.
Apache Tomcat/4.0.4 - HTTP Status 500 - Internal Server Error
type Exception report
message Internal Server Error
description The server encountered an internal error (Internal Server Error) that
pre
Apache Tomcat/4.0.4 - HTTP Status 503 - Servlet rpcrouter is currently unavailable
type Status report
message Servlet rpcrouter is currently unavailable
description The requested service (Servlet rpcro
Bruce,
I would be interested in seeing the screens (the links below don't seem to
work) and code changes. There is no one else currently working to improve
the admin UI.
Scott Nichol
- Original Message -
From: "Bruce Van Horn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, S
Scott,
You're amazing. Thanks for all the help. I'll let you know if I find any
bugs.
Chris Pittman
eWorker Technologies
-Original Message-
From: Scott Nichol [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 30, 2002 6:42 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Apach
If the parser supports namespaces correctly, you should not have this
problem.
If you want more help on this list, the things to post are
1. versions of software used (e.g. JDK, Apache SOAP, XML parser, servlet
container, OS)
2. capture of the messages being sent, e.g. using TcpTunnelGui
Scott
Hello,
there's a method to set output's namespace?
I have this problem:
SOAP protocol error: Unable to resolve namespace URI for 'xsd'
I read the following faq: 1.2 Help! I'm getting this error: "Unable to
resolve namespace URI for 'xsd'"
but my project needs pareser different from
