Soap4r: storing wiredump XMLs to a string

ruby-talk
1

str = “”
driver.wiredump_dev = str
puts str

will store HTTP request header, request SOAP XML, response HTTP header
and response SOAP XML to str. But you want to store only XMLs, not to file,
right?

Thanks for the response.

I will make a little clearer what i want to do.
In the apache axis soap package as well as in the MS .NET framework is it possible to install so called “custom soap handlers”. Such objects are called when a soap call is made and it is possible to perform addition work on the soap xml document in the handler class. A small example: my soap client calls a web service. Without a so called handler, the call is performed as normal. With the handler, to the outgoing soap xml document is added an xml element with the ruby version. So, on the server side i can count how much clients work with ruby 1.6 or 1.8. Sounds strange? Possible…

Roland

2

Hi,

From: SchmittR@t-systems.com
Sent: Friday, November 28, 2003 5:22 PM

I will make a little clearer what i want to do.
In the apache axis soap package as well as in the MS .NET framework is
it possible to install so called “custom soap handlers”. Such objects
are called when a soap call is made and it is possible to perform
addition work on the soap xml document in the handler class. A small
example: my soap client calls a web service. Without a so called
handler, the call is performed as normal. With the handler, to the
outgoing soap xml document is added an xml element with the ruby
version. So, on the server side i can count how much clients work
with ruby 1.6 or 1.8.

Thank you for well baked explanation. Perhaps I now understand your
request. You want to edit SOAPHeader part of XML, after/before your
client/server processes SOAPBody part, right?

<?xml version="1.0" encoding="utf-8" ?>

<env:Envelope xmlns:env=“http://schemas.xmlsoap.org/soap/envelope/”>
env:Header

<!-- add/check this element?? -->
<n1:ruby_info>
  <version>1.8.1</version>
  <release_date>2003-11-8</release_date>
</n1:ruby_info>

</env:Header>
env:Body
<n2:some_request …/>
</env:Body>
</env:Envelope>

I’m afraid I must say “not yet supported…”

Sounds strange? Possible…

Not strange. Fair enough. In the current developping code in my
workspace (not yet commited), there are headerHandler implementations
named lib/soap/header/handler.rb or so. Still halfway. I’ll back
to the development after 1.8.1-preview3 release…

Regards,
// NaHi