You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Adnan Fida <af...@point2.com> on 2001/05/23 19:06:31 UTC
Unsubscribe Me
Unsubscribe Me
-----Original Message-----
From: sanjiva@apache.org [mailto:sanjiva@apache.org]
Sent: Wednesday, May 23, 2001 10:32 AM
To: xml-soap-cvs@apache.org
Subject: cvs commit: xml-soap/java/docs/trouble index.html
sanjiva 01/05/23 09:31:56
Modified: java/docs intro.html
java/docs/install index.html
Added: java/docs/trouble index.html
Log:
putting troubleshooting stuff together
Revision Changes Path
1.6 +3 -2 xml-soap/java/docs/intro.html
Index: intro.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/intro.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- intro.html 2001/05/23 15:53:25 1.5
+++ intro.html 2001/05/23 16:31:37 1.6
@@ -16,8 +16,9 @@
<p>Apache SOAP is an open-source implementation of the <a
href="http://www.w3.org/TR/SOAP">SOAP v1.1</a> and <a
href="http://www.w3.org/TR/SOAP-attachments">SOAP Messages with
-Attachments</a> specifications. Apache SOAP is developed by the <a
-href="http://xml.apache.org/soap">Apache SOAP</a> community.</p>
+Attachments</a> specifications in Java. Apache SOAP is developed
+by the <a href="http://xml.apache.org/soap">Apache SOAP</a>
+community.</p>
<p>Apache SOAP can be used as a client library to invoke SOAP
services available elsewhere or as a server-side tool to
1.20 +14 -59 xml-soap/java/docs/install/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/index.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- index.html 2001/05/22 04:06:55 1.19
+++ index.html 2001/05/23 16:31:48 1.20
@@ -16,6 +16,18 @@
instructions for both cases and also has a trouble shooting
section to help sort out common installation related problems.</p>
+<p><strong>Important note for users upgrading from older versions
+of Apache SOAP: </strong>If you are upgrading from an older
+version of Apache SOAP then you must be sure to remove any cached
+class files, DeployedServices.ds files etc. or you will get a
+variety of strange errors. If you deployed Apache SOAP using a
+Web app, then any old expanded WARs must also be removed.
+Services deployed into the old version cannot be automatically
+transferred to the new version - you must manually re-deploy them
+to the new version. That is, the old DeployedServices.ds file
+cannot be read by this new version. We apologize in advanced for
+the pain this will cause some of our users.</p>
+
<h2>Unpack the Distribution</h2>
<p>We assume that you have downloaded the binary distribution of
@@ -141,64 +153,7 @@
<p>If this succeeds you will see it return with no output or with
a list of URIs. Either case is successful - it indicates what
services are already deployed on your server. If you get anything
-else then its time to troubleshoot. The table below identifies
-some common problems you may see and potential solutions.</p>
-
-<table border="1" width="100%">
- <tr>
- <th width="25%">Problem</th>
- <th width="50%">Comments</th>
- </tr>
- <tr>
- <td width="25%">You see the following message:<p><em>Ouch,
- the call failed:<br>
- Fault Code = SOAP-ENV:Server.Exception:<br>
- Fault String = org.w3c.dom.Node: method
getNamespaceURI()Ljava/lang/String;
- not found</em></p>
- </td>
- <td width="50%">Classpath is not set correctly: you still
- have some old parser or some other JAR file that has the
- org.w3c.dom.* classes <em>ahead</em> of a non-namespace
- aware parser. Please follow the installation instructions
- carefully again and verify you did everything right. If
- you start the server on a command line, type "javap
- org.w3c.dom.Node" and see whether you see<blockquote>
- <p><em>public abstract java.lang.String
- getNamespaceURI();</em></p>
- </blockquote>
- <p>in the output. If not, you still have a problem. Even
- if you do, you still have to make sure that your server
- configuration does not introduce some other parser ahead
- of the user classpath at startup time. (The default setup
- in Tomcat does this, for example.)</p>
- </td>
- </tr>
- <tr>
- <td width="25%">Exception in thread "main"
java.lang.NoClassDefFoundError:
- javax/activation/DataSource</td>
- <td width="50%">Classpath is not set correctly: add
<strong>activation.jar</strong>
- from <a
- href="http://java.sun.com/products/javabeans/glasgow/jaf.html"
- target="_top">Java Activation Framework</a> to your
- classpath.</td>
- </tr>
- <tr>
- <td width="25%">Exception in thread "main"
java.lang.NoClassDefFoundError:
- javax/mail/MessagingException</td>
- <td width="50%">Classpath is not set correctly: add
<strong>mail.jar</strong>
- from <a
- href="http://java.sun.com/products/javamail/index.html"
- target="_top">JavaMail</a> to your classpath.</td>
- </tr>
- <tr>
- <td width="25%">Exception in thread "main"
java.lang.NoClassDefFoundError:
- javax/xml/parsers/DocumentBuilderFactory</td>
- <td width="50%">Class is not set correctly: add a <a
- href="http://java.sun.com/xml/xml_jaxp.html"
- target="_top">JAXP</a> compatible, namespace-aware XML
- parser such as <a href="http://xml.apache.org/xerces-j">Apache
- Xerces</a> to your classpath.</td>
- </tr>
-</table>
+else then its time to <a href="../trouble/index.html">troubleshoot</a>.
+</p>
</body>
</html>
1.1 xml-soap/java/docs/trouble/index.html
Index: index.html
===================================================================
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
<title>Troubleshooting</title>
</head>
<body bgcolor="#FFFFFF">
<h2 align="center">Troubleshooting</h2>
<p>If you came here then something has gone wrong. Let's see
whether we can help you find what's causing the problem and fix
it. Yes, the stuff does work and yes the samples do work .. at
least for us :-). Now let's try to make them work for you.</p>
<p>The table below has a list of common problems and possible
solutions. Do you see your problem listed?</p>
<table border="1" width="100%">
<tr>
<th width="25%">Problem</th>
<th width="50%">Comments</th>
</tr>
<tr>
<td width="25%">You see the following message:<p><em>Ouch,
the call failed:<br>
Fault Code = SOAP-ENV:Server.Exception:<br>
Fault String = org.w3c.dom.Node: method
getNamespaceURI()Ljava/lang/String;
not found</em></p>
</td>
<td width="50%">Classpath is not set correctly: you still
have some old parser or some other JAR file that has the
org.w3c.dom.* classes <em>ahead</em> of a non-namespace
aware parser. Please follow the installation instructions
carefully again and verify you did everything right. If
you start the server on a command line, type "javap
org.w3c.dom.Node" and see whether you see<blockquote>
<p><em>public abstract java.lang.String
getNamespaceURI();</em></p>
</blockquote>
<p>in the output. If not, you still have a problem. Even
if you do, you still have to make sure that your server
configuration does not introduce some other parser ahead
of the user classpath at startup time. (The default setup
in Tomcat does this, for example.)</p>
</td>
</tr>
<tr>
<td width="25%">Exception in thread "main"
java.lang.NoClassDefFoundError:
javax/activation/DataSource</td>
<td width="50%">Classpath is not set correctly: add
<strong>activation.jar</strong>
from <a
href="http://java.sun.com/products/javabeans/glasgow/jaf.html"
target="_top">Java Activation Framework</a> to your
classpath.</td>
</tr>
<tr>
<td width="25%">Exception in thread "main"
java.lang.NoClassDefFoundError:
javax/mail/MessagingException</td>
<td width="50%">Classpath is not set correctly: add
<strong>mail.jar</strong>
from <a
href="http://java.sun.com/products/javamail/index.html"
target="_top">JavaMail</a> to your classpath.</td>
</tr>
<tr>
<td width="25%">Exception in thread "main"
java.lang.NoClassDefFoundError:
javax/xml/parsers/DocumentBuilderFactory</td>
<td width="50%">Class is not set correctly: add a <a
href="http://java.sun.com/xml/xml_jaxp.html"
target="_top">JAXP</a> compatible, namespace-aware XML
parser such as <a href="http://xml.apache.org/xerces-j">Apache
Xerces</a> to your classpath.</td>
</tr>
</table>
<h2>Is it in the FAQ?</h2>
<p>If you are down here then you're probably still looking. We
feel for you. Let's go to the next level: is your problem listed
in one of the FAQs? Please look at <a
href="http://xml.apache.org/soap/faq">http://xml.apache.org/soap/faq</a>.</p
>
<h2>Have others had this problem?</h2>
<p>Oh oh, life's not good today. OK, last resort- please join the
<a href="mailto:soap-user@xml.apache.org">soap-user@xml.apache.org</a>
mailing list and ask there. Odds are that your problem has been
run into before and someone there will know what to do.</p>
<h2>Is it a bug?</h2>
<p>If you believe that you have found a bug in the code, please
visit <a href="http://xml.apache.org/soap">http://xml.apache.org/soap</a>
and file a bug report using Bugzilla. Before filing a report
please, please search and see whether it has already been
reported by someone else.</p>
<p>Thanks for your patience. Please accept our deepest sympathies
for the pain you are in. We feel your pain.</p>
</body>
</html>