Loading ...
Sorry, an error occurred while loading the content.

3218does it make sense to give no return value?

Expand Messages
  • Tilman Baumann
    Dec 8, 2003
    • 0 Attachment

      i have a funktion at the serverside wich adds an element to a database.
      This funktion has a appropriate errorhandling with die's. (Throwing
      exceptions with die seens to be a nice idea to generate a soapfault)

      I think it would not make any sense to give any return value in this
      funktion because if anything goes wrong i get a fault and if not all is

      Is that the right thinking? What is the common way? Is it supposed to do
      this in this way?

      I get a empty <s-gensym3 xsi:type="xsd:string"/> back. That looks a bit
      strange. :) (soapreturn below)

      Thank you for answer.

      Date: Mon, 08 Dec 2003 10:24:25 GMT.
      Server: libwww-perl-daemon/1.25.
      Content-Length: 545.
      Content-Type: text/xml; charset=utf-8.
      SOAPServer: SOAP::Lite/Perl/0.55.
      <?xml version="1.0" encoding="UTF-8"?>
      <SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
      <namesp1:addResponse xmlns:namesp1="http://www.ben-hur.de/Updateserver"
      Tilman Baumann

      pyramid computer GmbH
      Boetzinger Strasse 60 D-79111 Freiburg

      They who would give up an essential liberty for temporary security, deserve
      neither liberty or security
      - Benjamin Franklin
    • Show all 4 messages in this topic