AW: [soaplite] SOAP::SOM question
- This one crops up every once in a while, I had to search myself :-)Let your handler module inherit from SOAP::Server::Parameters, i.e. simply put that into your @ISA array, and - voilà - you've got an additional parameter after the hash. This parameter is a real SOAP::SOM object. It's not as easy to navigate as the hash, but it gives you access not only to repeating elements but also to attributes.The rule is: use the hash for simple parameters without attributes, use the SOM object in all other cases. As you get both, you may even mix these two styles, using the SOM object only for what you can't get out of the hash.Hope that helps
Dipl.Ing. Andreas Manessinger - CCT / Competence Center Telematik
Magistrat der Stadt Wien, Magistratsabteilung 14 - ADV,
Rathausstr. 1, A-1082 Wien
Tel: (+43 1) 4000-91176
Fax: (+43 1) 4000-99-91176
Von: teden *EXTERN* [mailto:the@...]
Gesendet: Mittwoch, 27. August 2003 18:57
Betreff: [soaplite] SOAP::SOM question
I am building a web service in SOAP::Lite. Part of the results
returned is a set of repeating elements e.g.
On my client side, with trace on, I see the whole XML document, with
all of the elements listed. However, when I try to process the
results in my client, SOAP::Lite is pushing this into a nested hash
structure. Hence, when I go to get my statusMsg's, I am left with
only the last one, the first two are lost. Any kind of repeating
element does the same thing.
Is there any way around this?
Any help is greatly appreciated...
To unsubscribe from this group, send an email to:
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.