Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • this puts paid to some of the FUD about Java's stronger and 'native' xml support.

    Its all very having mature and stable xml support - but I'd rather have perls ability to 'just work'.

    acme have you tried with .Net after all thats supposed to be where web services, xml and SOAP are at..


    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • by ziggy (25) on 2002.08.19 11:12 (#11933) Journal
      this puts paid to some of the FUD about Java's stronger and 'native' xml support.
      That's not a fair assessment of what Leon described. Apache-SOAP had this dependency on mail handling, because as we all know, email is a key component in web services (and I'm only half joking).

      In reality, the problem is with SOAP. It's a very big spec, difficult to implement fully (and properly!), so there are lots of interoperability problems. Had Vx been coded with Apache-SOAP from the start (in Java), then I suspect that a lot of these integration issues wouldn't crop up (but you'd have to deal with programming it all in Java).

      The big problem sounds like the lack of WSDL files for the SOAP services. This is pretty much expected, since WSDL is a statically typed interface spec that can be autogenerated from Java/C# code reasonably easily; doing the same from dynamically typed Perl code is a much more difficult nut to crack. And having the WSDL code would help, but wouldn't eliminate all of the interoperability headaches between SOAP implementations.

      At least SOAP::Lite just works. :-)

      • Right, Perl is just too dynamic for WSDL really. That's why Pierre thought up the very clever WSDL::Generator, so all we need to do is figure out why it doesn't work with 5.8 and then run the test suite with it installed. With any luck, a fully-specced WSDL will fall out. I'll try again when we have this...