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.
  • 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:

      <SOAP-ENV:Header><namesp3:My__Class xmlns:namesp3="http://namespaces.soaplite.com/header" xsi:type="namesp2:My__Class"><_new xsi:type="xsd:string">bar</_new></namesp3:My__Class></SOAP-ENV:Header><SOAP-ENV: Body><namesp4:methodResponse xmlns:namesp4="http://my.server.com/My/Class"><s-gensym7 xsi:type="xsd:string">new: </s-gensym7><s-gensym9 xsi:type="xsd:string">bar</s-gensym9><s-gensym11 xsi:type="xsd:string">, method: beer</s-gensym11></namesp4:methodResponse></SOAP-ENV:Body>