Re: [soapbuilders] mustUnderstand testing

[Simon Fell <so...@zaks.demon.co.uk>]

Hmmm, this is what i get back,

<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>mustUnderstand</faultcode>
<faultstring>Didn't understand header 'Transaction'</faultstring>
<faultactor>/soap/servlet/rpcrouter</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Shouldn't the faultcode be SOAP-ENV:mustUndertstand ?

Cheers
Simon

On Tue, 3 Apr 2001 03:58:29 -0700, in soap you wrote:

>The apache ilab service has now been configured for mustUnderstand.
>
>cheers, tony
>
>> -----Original Message-----
>> From: Simon Fell [mailto:soap@zaks.demon.co.uk]
>> Sent: Monday, April 02, 2001 10:39 AM
>> To: soapbuilders@yahoogroups.com
>> Subject: Re: [soapbuilders] mustUnderstand testing
>>
>>
>> Glen,
>>
>> That's great (ignore the other mail i just sent, i hadn't gotten this
>> far yet down my mail yet !). Tony, can you tweak the Apache deployment
>> for this ?, do you have enough to go on ?
>>
>> Cheers
>> Simon
>>
>>
>> On Mon, 2 Apr 2001 09:07:54 -0400, in soap you wrote:
>>
>> >> I added another test to my pocketSOAP suite, that sends a echoString
>> >> request, with a header set to mustUnderstand=1, and looked to see how
>> >> many servers handled it correctly (by returning a soap fault)
>> >>
>> >> Not a single one passed
>> >>
>> >> Apache 2.1 (returned the string)
>> >
>> >I added the faulting capability for mustUnderstand to Apache
>> post-2.1, and
>> >there is a small tweak you need to make to switch it on -
>> namely, you must
>> >add a "checkMustUnderstands='true'" attribute to the
>> <isd:service> element
>> >in your deployment descriptor.  This attribute tells the engine that your
>> >service isn't going to be implementing header semantics itself, and
>> >therefore it should fault on any mustUnderstand="1" header.  I
>> did it this
>> >way to avoid breaking any pre-existing services; otherwise we would have
>> >needed some way of indicating which headers a given service
>> "understands",
>> >and that means pre-change services might have ended up faulting when they
>> >actually did understand a given header.
>> >
>> >In Axis we're implementing full header-processing, so this will just work
>> >out of the box.
>> >
>> >--Glen
>> >
>> >
>> >
>> >
>> >To unsubscribe from this group, send an email to:
>> >soapbuilders-unsubscribe@yahoogroups.com
>> >
>> >
>> >
>> >Your use of Yahoo! Groups is subject to
>http://docs.yahoo.com/info/terms/
>>
>
>
>
>To unsubscribe from this group, send an email to:
>soapbuilders-unsubscribe@yahoogroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>------------------------ Yahoo! Groups Sponsor ---------------------~-~>
>Do you have 128-bit SSL encryption server security?
>Get VeriSign's FREE Guide, "Securing Your
>Web Site for Business." Get it now!
>http://us.click.yahoo.com/2cW4jC/c.WCAA/bT0EAA/WNqXlB/TM
>---------------------------------------------------------------------_->
>
>To unsubscribe from this group, send an email to:
>soapbuilders-unsubscribe@yahoogroups.com
>
> 
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
>