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

339Re: [soaplite] java client for SOAP::Lite server

Expand Messages
  • Paul Kulchenko
    May 16, 2001
      Hi, Douglas!

      Right. It works this way. The only thing that SOAP::Lite server does
      magically is returning modified object back on client side. Say you
      have an object on client side. When you make a call object itself can
      be modified, but there is no way to return modified object (because
      result of call is returned), so SOAP::Lite returns object as a SOAP
      Header. Client side will recover it and update your object
      accordingly. You can do the same thing in Java client, but you need
      to write this code yourself. Everything will work WITHOUT this piece,
      only Java client won't be able to see changes in object that came
      from server side (if any).

      Everything else is just "formatted text strings", no magic there :))

      > directly to make a message and LWP::UserAgent to send it rather
      In fact you can reuse Client libraries calling send_receive method,
      in that case you can get M-POST, redirects, and all low level code.
      Almost all components can be used separately. Be warned however about
      planned changes in send_receive interface. There will be more
      communications between Serializer, Transport and Deserializer. I'm
      making those changes as much compatible with current code as
      possible, but undocumented features may not work as worked before.

      Best wishes, Paul.

      --- Douglas Bonar <Doug.Bonar@...> wrote:
      > Christof Damian wrote:
      > >
      > > > > all the examples i found on the net don't seem to return
      > objects,
      > > > > just simple types (temperature, stockquote, ...)
      > > > You may take a look into examples/oo-apache.pl which accesses
      > object
      > > > returned by ApacheSOAP implementation.
      > >
      > > i saw that, but i want it the other way around. i would like to
      > see a
      > > java client for a SOAP::Lite server.
      > >
      > > the client should dispatch them remotely.
      > >
      > > christof
      > I know this is the brute force way, but it works if you control
      > the server. Just set the server to dump incoming and outgoing
      > messages
      > to a file and then use the Perl client to talk to it. After you
      > have
      > captured the messages, you can use whatever Java XML or SOAP
      > package
      > you want to send equivalent messages. SOAP-Lite isn't doing
      > anything
      > magical (though it sometimes looks that way), it is just
      > serializing
      > the function arguments into SOAP and reconstructing them at the
      > other end. (And I don't mean that disparagingly at all.)
      > Underneath
      > it is all just specially formatted text strings.
      > I'ld include an example, but my Java clients have all used
      > a locally produced library so my examples wouldn't help. The
      > effect
      > was more like working with SOAP::Data and SOAP::Serializer classes
      > directly to make a message and LWP::UserAgent to send it rather
      > than
      > using autodispatch. But it was fairly workable.
      > Doug
      > To unsubscribe from this group, send an email to:
      > soaplite-unsubscribe@yahoogroups.com
      > Your use of Yahoo! Groups is subject to
      > http://docs.yahoo.com/info/terms/

      Do You Yahoo!?
      Yahoo! Auctions - buy the things you want at great prices
    • Show all 5 messages in this topic