RE: Deploy Error

[davout]

Title: Deploy Error

Thanks.... but I'm not sure if that's necessarily what I'm after.

 

Basically if you're employing source from other projects you need to advise us what the version/time line we need to include from those other projects.

 

For instance are you using Xerces 1 or Xerces 2??  If its Xerces 1 then is it Xerces V1.4.4? Or if its Xerces 2 is it V2.0.2??

 

Get the idea?

 

 

-----Original Message-----
From: Snigdha Pandit [mailto:[EMAIL PROTECTED]]
Sent: 21 June 2002 16:07
To: [EMAIL PROTECTED]
Subject: RE: Deploy Error

hi,

 

i have attached the xerces.jar i used to solve this problem.

 

hope this helps

 

regards

snigdha

-----Original Message-----
From: davout [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 8:38 PM
To: [EMAIL PROTECTED]
Subject: RE: Deploy Error

whats the oldest Xerces version number that should be used?

 

 -----Original Message-----
From: Snigdha Pandit [mailto:[EMAIL PROTECTED]]
Sent: 21 June 2002 15:03
To: [EMAIL PROTECTED]
Subject: RE: Deploy Error

hi,

 

 

Check the version of the xerces parser you are using.

 

Older versions of Xerces do not have a parse method that has the following signature

    parse(InputSource inputSource, DefaulHandler handler)

 

regards

snigdha

 

-----Original Message-----
From: The Hoa Nguyen [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 6:28 PM
To: '[EMAIL PROTECTED]'
Subject: Deploy Error

Hi All,

I am very new to Axis. I've just installed Axis beta2. After the installation, I follow the guides in the sample readme file to try to deploy the service there. I started the simple Axis server and tried to deploy a sample service. And I got the following exceptions at the client and server side:

Client side:

[INFO] AdminClient - -Processing file deploy.wsdd
[ERROR] AdminClient - -AxisFault: AxisFault
 faultCode: http://xml.apache.org/axis/:HTTP
 faultString:
 faultActor: null
 faultDetail:
        null: return code:  0

Server side

[INFO] SimpleAxisServer - -SimpleAxisServer starting up on port 8080.
Exception in thread "main" java.lang.NoSuchMethodError
        at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:202)
        at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:428)
        at org.apache.axis.Message.getSOAPEnvelope(Message.java:306)
        at org.apache.axis.handlers.soap.SOAPService$SOAPRequestHandler.invoke(SOAPService.java:138)
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:154)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:121)
        at org.apache.axis.server.AxisServer.invoke(AxisServer.java:288)
        at org.apache.axis.transport.http.SimpleAxisServer.run(SimpleAxisServer.java:385)
        at org.apache.axis.transport.http.SimpleAxisServer.main(SimpleAxisServer.java:811)

I used the same CLASSPATH for both case.
My CLASSPATH include the following jar file in order: xerces.jar, axis.jar, jaxrpc.jar, commons-logging.jar, tt-bytecode.jar, log4j-core.jar and the sample classes.

I don't know if I made any mistake in the case. I am completed stucked at these steps.
I will very appreciate if anyone can help me.
Thanks alot.
The Hoa

Power your enterprise with custom solutions in eLearning and Knowledge Management from NIIT - Knowledge Solutions. For details visit our website http://www.ksb.niit.com

___________________NOTICE____________________________

This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please notify the sender by reply e-mail and then destroy the message. Opinions, conclusions, and other information in this message that do not relate to the official business of NIIT shall be understood to be neither given nor endorsed by NIIT When addressed to NIIT clients, any information contained in this e-mail is subject to the terms and conditions in the governing client contract.