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
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
I'm trying to call the Apache SOAP 2.2 sample
AddressBook::getAllListings, which is a literal XML request/response.
The Apache based client works, the equivalent pocketSOAP code produces
an error, i can't see why,
Here's the Apache generated request that works
http://schemas.xmlsoap.org/soap/en
Looking through the 2.2 source, it appears that RPCMessage::unmarshal
works out the correct encodingStyle URL, but then passes the wrong
version to the call constructor. This doesn't trip up the Apache
client because RPCRouter::invoke will pull the encodingStyle from the
first child of the body if
lue) vector.get(0);
> BrandMasterValue brandMasterValue2 = (BrandMasterValue) vector.get(1);
> return new String("FIRST BRAND MASTER IS = " +
>brandMasterValue1.getBrand() + " THE SECOND IS " +
>brandMasterValue2.getBrand());
> }
>}
>
>public cla
This turns out to be a bug in VectorSerializer, it never checks /
de-references the hrefs. I've attached a patch.
John, one final tweak you'll need to your pocketSOAP client code, is
when setting the brand property, to wrap the values in a CLng call, as
the Apache end doesn't do type promotions.
That correct for calling MS Toolkit 2.0 services, but not for .NET.
.NET by default does doc/literal SOAP, not rpc/encoded, you're sending
an rpc/encoded message, which .NET will largely ignore. You need to
send a doc/literal request. Not sure how you cook those up with the
2.2 code.
Cheers
Simo
It will de-serialize href's, as long as they don't form circular
references (in which case it goes round in circles til the stack runs
out). It doesn't serialize hrefs.
AIUI, all these issues are fixed in Axis.
Cheers
Simon
On Fri, 5 Apr 2002 15:14:40 -0500, in soap you wrote:
>Do you know whe
I noticed that Apache SOAP always serializes NULLs with
xsi:null="true", the problem is that for the 2001 schema version there
is no null attribute it got renamed to nil.
The quick fix is to change the definition of ATTR_NULL in
constants.java, however it looks like the code supports both 1999 an
blem and probably sufficient cause for a 2.3.1 to be
>released ASAP.
>
>I agree it needs to be fixed right to work with both XSD
>versions.
>
>Thanks!
>
>Sanjiva.
>
>- Original Message -
>From: "Simon Fell" <[EMAIL PROTECTED]>
>To: <[EMA
ions.
>
>Thanks!
>
>Sanjiva.
>
>- Original Message -
>From: "Simon Fell" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Saturday, June 08, 2002 8:45 AM
>Subject: xsi:null handling
>
>
>> I noticed that Apache SOAP always serializ
FYI, there's some bugs in this, all the HTTP header line endings
should be \r\n not just \n
Cheers
Simon
On 1 Aug 2002 03:07:32 -, in soap you wrote:
>snichol 2002/07/31 20:07:32
>
> Modified:java/docs changes.html
> java/src/org/apache/soap/util/net SSLUtils.java
>
12 matches
Mail list logo
