Should I actually HAVE objects on the application end of the code?

In my opinion, no. I prefer SOAP interfaces to remain as simple as possible, working on scalar arguements and returning simple structures (single-level arrays or hashes, if possible). If you start passing objects back and forth you'll open yourself up to SOAP's difficulty dealing with large amounts of data, the complexity of SOAP's encode/decode model as well as losing any potential for non-Perl clients to access your service.

I don't have answers to your other questions. Have you tried the SOAP::Lite list? Back when I was mired deep in SOAP I found it to be helpful.

-sam

PS: When you think you've had enough of SOAP, take a look at this: Don't Be Afraid to Drop the SOAP.

In reply to Re: First Forays into SOAP by samtregar
in thread First Forays into SOAP by japhy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.