It would be helpful if you could post a copy of the deployment descriptor. Short of
that, from the
error, I am wondering whether you have an attribute in the XML typed "iD" instead of
"id".
Scott Nichol
- Original Message -
From: "David Zufferey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTEC
Things that would help:
1. What code are you running?
2. What is the error number and/or text?
3. What version of VB and SOAP Toolkit are you using?
Scott
- Original Message -
From: "Vaibhav Joshi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 19, 2002 5:10 PM
Subject
Generally, the samples accept a command line parameter specifying the endpoint
URL for the SOAP server. The test scripts use
http://localhost:8080/soap/servlet/rpcrouter. You will get an error like the
one you report if there is no processing listening on the server port. When
running the tests
This is documented in Apache SOAP docs. Go to User Guide, then
Interoperability. You will see that there is a workaround for this.
Scott Nichol
- Original Message -
From: "Paco Avila" <[EMAIL PROTECTED]>
To: "SOAP Developer" <[EMAIL PROTECTED]>; "SOAP User"
<[EMAIL PROTECTED]>
Sent: Mo
What modules are you using. xerces? which version... etc.
If we know this, we can continue.
Thx,
Henk.
-Original Message-
From: Sharad Patel [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 07 February, 2002 6:26 AM
To: [EMAIL PROTECTED]
Subject: Error : BadTargetObjectURI
I have a simple w
Title: WSDL descriptors
Tuan,
There
is a fix for the toolkit. It might work.
Have a
look at:
http://windows.oreilly.com/news/soap_0800.html
http://windows.oreilly.com/news/soapreview_0600.html
There
you will also find info about the fix for the toolkit.
Regards,
Henk.
-Orig
ache.soap.encoding.soapenc.BeanSerializer"/>
>
>Please advice..!
>Thanks
>
>-Original Message-
>From: Simon Fell [mailto:[EMAIL PROTECTED]]
>Sent: Friday, November 16, 2001 3:37 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Error: SOAP-ENV:Client No Deserializer foun
Customer Account List Service
http://localhost:7001/soap/servlet/rpcrouter"/>
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 16, 2001 3:22 PM
To: [EMAIL PROTECTED]
Subject: Re: Error: SOAP-ENV:Client No Deserializer found to deserialize
What does your WSDL file look like for this method?
Please advice..!
Thanks
-Original Message-
From: Simon Fell [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 16, 2001 3:37 PM
To: [EMAIL PROTECTED]
Subject: Re: Error: SOAP-ENV:Client No Deserializer found to deserialize
On Fri, 16 Nov 2001 15:11:44 -0500, in soap you wrote:
>all,
>
What does your WSDL file look like for this method?
On Fri, 16 Nov 2001 15:11:44 -0500, in soap you wrote:
>all,
>
>I have been trying to figure out why I keep getting the error below:
>
>Entries: SOAP-ENV:Client No Deserializer found to deserialize a
>':meth1_inType' using encoding style
>'http://schemas.xmlsoap.org/soap/encoding/'. /soap/servl
I believe you are loading an XML parser that does not support namespaces.
Scott
- Original Message -
From: "Shaffin Bhanji" <[EMAIL PROTECTED]>
To: "SOAP DEV (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, July 04, 2001 2:57 PM
Subject: Error during Envelope.unmarshall()
> Hell All,
>
>
hi , cleveland:
perhaps you forgot to
set the client's classpath.
please try again,or let's know your detail
envionment.
- Original Message -
From:
cleveland cooke
To: [EMAIL PROTECTED]
Sent: Thursday, May 31, 2001 9:00
PM
Subject: error using tomcat
Yes
Go to the tomcat.bat file under the
\jakarta-tomcat\bin\ folder and find the following occurrence:
set CP=%CP%;%CLASSPATH% and change it with the
following one
set
CP=%CLASSPATH%;%CP%
There is a comment in the installation docs about
this procedure...
I hope it helps you
14 matches
Mail list logo