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

Re: Change SOAPsh.pl to display all returned arguments

Expand Messages
  • Paul Kulchenko
    Hi, Chris! Thanks for the patch, I ll use it. Actually I plan couple of changes in SOAPsh.pl: 1. change print() to warn() on invitation and warn() to print()
    Message 1 of 2 , May 4, 2001
    View Source
    • 0 Attachment
      Hi, Chris!

      Thanks for the patch, I'll use it. Actually I plan couple of changes
      in SOAPsh.pl:
      1. change print() to warn() on invitation and warn() to print() on
      output, so it will be easy to redirect output somewhere.
      2. drop $VAR1 and leave only dump
      3. add shell as shell() function in SOAP::Lite, so you'll be able to
      call SOAPsh.pl or use 'perl -MSOAP::Lite -e shell' (still not sure
      how good this idea is)
      4. probably provide ReadLine capabilities (show previous command,
      edit it, etc.)
      5. add ability to assign/use variables (still not sure also)

      Does anybody need it?

      Best wishes, Paul.

      --- Chris Davies <Chris.Davies@...> wrote:
      > Here's a little unidiff for SOAPsh.pl that displays all return
      > arguments
      > rather than just the first one. I know it could be make more
      > complex - but I
      > don't think that's the point of SOAPsh.pl, is it.
      >
      > Regards,
      > Chris
      >
      > --- /usr/bin/SOAPsh.pl Mon Apr 30 11:40:26 2001
      > +++ mySOAPsh.pl Fri May 4 12:06:50 2001
      > @@ -22,7 +22,7 @@
      > ? warn(join "\n", "--- METHOD
      > RESULT ---", $res || '', '') :
      > defined($res) && $res->fault ? warn(join "\n", "--- SOAP
      > FAULT ---",
      > $res->faultcode, $res->faultstring, '') :
      > !$soap->transport->is_success ? warn(join "\n", "---
      > TRANSPORT
      > ERROR ---", $soap->transport->status, '') :
      > - warn(join "\n", "--- SOAP
      > RESULT ---",
      > Dumper($res->result), '')
      > + warn(join "\n", "--- SOAP
      > RESULT ---",
      > Dumper($res->result), Dumper($res->paramsout), '')
      > } continue {
      > print "\n> ";
      > }
      >
      > --
      > Chris Davies, Manheim Interactive (Europe)
      > Tel. 0870 444-0450 Fax. 0870 444-0482 Email.
      > MOL@...
      >


      __________________________________________________
      Do You Yahoo!?
      Yahoo! Auctions - buy the things you want at great prices
      http://auctions.yahoo.com/
    • Chris Davies
      Personally I think that SOAPsh.pl should be short, fast, and effective. It seems to me that in real world applications it s unlikely you re going to be able to
      Message 2 of 2 , May 4, 2001
      View Source
      • 0 Attachment
        Personally I think that SOAPsh.pl should be short, fast, and effective.

        It seems to me that in real world applications it's unlikely you're going to
        be able to code up all the appropriate parameters manually, so SOAPsh.pl
        will have to be replaced with a custom test-bed environment anyway. The more
        complex SOAPsh.pl is, the harder it's going to be for folk to
        reverse-engineer it to see how it works.

        I use SOAPsh.pl as a command line application, viz
        SOAPsh.pl 'http://192.168.1.1/service.cgi' 'Demo' 'readable(1)'
        'on_debug(sub{print @_})'

        Regards,
        Chris


        -----Original Message-----
        From: Paul Kulchenko [mailto:paulclinger@...]
        Sent: Friday, May 04, 2001 4:23 PM
        To: Chris Davies
        Cc: soaplite@yahoogroups.com
        Subject: Re: Change SOAPsh.pl to display all returned arguments



        Hi, Chris!

        Thanks for the patch, I'll use it. Actually I plan couple of changes
        in SOAPsh.pl:
        1. change print() to warn() on invitation and warn() to print() on
        output, so it will be easy to redirect output somewhere.
        2. drop $VAR1 and leave only dump
        3. add shell as shell() function in SOAP::Lite, so you'll be able to
        call SOAPsh.pl or use 'perl -MSOAP::Lite -e shell' (still not sure
        how good this idea is)
        4. probably provide ReadLine capabilities (show previous command,
        edit it, etc.)
        5. add ability to assign/use variables (still not sure also)

        Does anybody need it?

        Best wishes, Paul.

        --- Chris Davies <Chris.Davies@...> wrote:
        > Here's a little unidiff for SOAPsh.pl that displays all return
        > arguments
        > rather than just the first one. I know it could be make more
        > complex - but I
        > don't think that's the point of SOAPsh.pl, is it.
        >
        > Regards,
        > Chris
        >
        > --- /usr/bin/SOAPsh.pl Mon Apr 30 11:40:26 2001
        > +++ mySOAPsh.pl Fri May 4 12:06:50 2001
        > @@ -22,7 +22,7 @@
        > ? warn(join "\n", "--- METHOD
        > RESULT ---", $res || '', '') :
        > defined($res) && $res->fault ? warn(join "\n", "--- SOAP
        > FAULT ---",
        > $res->faultcode, $res->faultstring, '') :
        > !$soap->transport->is_success ? warn(join "\n", "---
        > TRANSPORT
        > ERROR ---", $soap->transport->status, '') :
        > - warn(join "\n", "--- SOAP
        > RESULT ---",
        > Dumper($res->result), '')
        > + warn(join "\n", "--- SOAP
        > RESULT ---",
        > Dumper($res->result), Dumper($res->paramsout), '')
        > } continue {
        > print "\n> ";
        > }
        >
        > --
        > Chris Davies, Manheim Interactive (Europe)
        > Tel. 0870 444-0450 Fax. 0870 444-0482 Email.
        > MOL@...
        >


        __________________________________________________
        Do You Yahoo!?
        Yahoo! Auctions - buy the things you want at great prices
        http://auctions.yahoo.com/
      Your message has been successfully submitted and would be delivered to recipients shortly.