ServiceManagerClient Problem

[David Turner <tu...@genome.wi.mit.edu>]

I've been getting the following exception when I run the
ServiceManagerClient, which, for the life of me, can't resolve.

9:35am turner@darwin
~/src/omnigene/edu/mit/wi/omnigene/soap/examples/SearchProjectList >
java org.apache.soap.server.ServiceManagerClient
http://darwin:8080/soap/servlet/rpcrouter deploy
DeploymentDescriptor.xml

Exception in thread "main" [SOAPException: faultCode=SOAP-ENV:Client;
msg=Parsing error, response was:
The markup in the document preceding the root element must be
well-formed.; targetException=org.xml.sax.SAXParseException: The markup
in the document preceding the root element must be well-formed.]
        at org.apache.soap.rpc.Call.invoke(Call.java, Compiled Code)
        at
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClient.java,

Compiled Code)
        at
org.apache.soap.server.ServiceManagerClient.deploy(ServiceManagerClient.java,

Compiled Code)
        at
org.apache.soap.server.ServiceManagerClient.main(ServiceManagerClient.java,

Compiled Code)




My system is configured the following way:
Unix
JDK1.3.0
JAXP1.1
SOAP2.2
JavaMail1.2
JAF1.0.1
Xerces1.4.1
Tomcat4.0beta


I've also attempted the above configuration on Linux (ReadHat 7.1) using

JDK1.4beta, and got a slightly different error:
"The root element is missing" exception.

I've managed to following the code to the point were I believe the
problem is occurring.  The soap request is good, but when the response
comes back the soap envelope is incomplete so closing tags are missing,
which would explain the parsing error.  The problem is that I can't
trace what's causing this on the server side.  I've check to insure that

my classpath is correct and that I'm not conflicting with any other
parsers.

I NEED SUGGESTIONS!  This problem has been ongoing for the entire week.

Any help would be greatly appreciated.

Re: ServiceManagerClient Problem

[William Brogden <wb...@bga.com>]

 I am betting it is a problem with old XML parser code being 
picked up. The first part of that error message is just due to
the ServiceManagerClient getting a non-xml error message back.
Look elsewhere for error messages that might provide a clue.

 When something like this happened to me it was eventually 
traced to a jar file in the JAVA_HOME\jre\lib\ext  directory
that Java looks at before looking at your classpath. 

David Turner wrote:
> 
> I've been getting the following exception when I run the
> ServiceManagerClient, which, for the life of me, can't resolve.
> 
> 9:35am turner@darwin
> ~/src/omnigene/edu/mit/wi/omnigene/soap/examples/SearchProjectList >
> java org.apache.soap.server.ServiceManagerClient
> http://darwin:8080/soap/servlet/rpcrouter deploy
> DeploymentDescriptor.xml
> 
> Exception in thread "main" [SOAPException: faultCode=SOAP-ENV:Client;
> msg=Parsing error, response was:
> The markup in the document preceding the root element must be
> well-formed.; targetException=org.xml.sax.SAXParseException: The markup
> in the document preceding the root element must be well-formed.]
>         at org.apache.soap.rpc.Call.invoke(Call.java, Compiled Code)
>         at
> org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClient.java,
> 
> Compiled Code)
>         at
> org.apache.soap.server.ServiceManagerClient.deploy(ServiceManagerClient.java,
> 
> Compiled Code)
>         at
> org.apache.soap.server.ServiceManagerClient.main(ServiceManagerClient.java,
> 
> Compiled Code)
> 
> My system is configured the following way:
> Unix
> JDK1.3.0
> JAXP1.1
> SOAP2.2
> JavaMail1.2
> JAF1.0.1
> Xerces1.4.1
> Tomcat4.0beta
> 
> I've also attempted the above configuration on Linux (ReadHat 7.1) using
> 
> JDK1.4beta, and got a slightly different error:
> "The root element is missing" exception.
> 
> I've managed to following the code to the point were I believe the
> problem is occurring.  The soap request is good, but when the response
> comes back the soap envelope is incomplete so closing tags are missing,
> which would explain the parsing error.  The problem is that I can't
> trace what's causing this on the server side.  I've check to insure that
> 
> my classpath is correct and that I'm not conflicting with any other
> parsers.
> 
> I NEED SUGGESTIONS!  This problem has been ongoing for the entire week.
> 
> Any help would be greatly appreciated.

-- 
WBB - wbrogden@lanw.com
Java Cert mock exams http://www.lanw.com/java/javacert/
Author of Java Developer's Guide to Servlets and JSP 
ISBN 0-7821-2809-2