Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Yeah, and remember--Perl's confusing because it lets you have two variables named the same thing!

    --Nat

  • in 2001 I wrote a client/server application in perl and C for my Degree. Later in the year I tried to replace the GTK/C application with a Java client.

    In short after 2 weeks I gave up. The URL Class didn't support any protocols other than FTP and HTTP , I had to convert between dozens of different objects, cast variables, and jump through hoops to do the same as a simple 5 line perl script.

    Unless there is a ready-build shrink-wrapped component Java connectivity is unnacceptable. The only use for Java is

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
  • I'm no expert, but it looks to me like the reason this doesn't work for Java or Python is because object-by-reference is explictly not part of SOAP: link [w3.org].

    The fact that SOAP::Lite provides a proprietary OBR mechanism is nice but certainly not something you should hold against other vendors for not implementing. Someone correct me if I'm wrong...

    • yeah, you may be right. chromatic thought it might not be part of the spec either, and maybe you're both right.

      however, because SOAP::Lite to SOAP::Lite does work (and work very well, I find it hard to believe that Java (or Python, or Ruby, or whatever) cannot be coerced into understanding SOAP::Lite objects.

      maybe it's just a matter of writing a java class that implements a serializer specific to understanding SOAP::Lite. after all, the contents of the envelope certainly look straightforward enough: