This is a simple answer addressed in an article I wrote for Builder.com entitled A Hands On Tour of SOAP::Lite. The answer is also answered, albeit indirectly, in a previous post about complex types. The secret is properly escaping the SOAP::Data element like so: \SOAP::Data. I know, it is not very intuitive. :-(
Documentation
Mailing Lists
Project Links
Recommended Books
Randy J. Ray: Programming Web Services with Perl
An excellent introduction to Web services, and to SOAP, XML-RPC and more. The reference in the back is an indespensible resource.
« How to add multiple namespaces to an element | Main | Parsing a result object from SOAP::Lite »
Comments
The comments to this entry are closed.
Don't Hate the Ads
Recent Comments
- Samia on Support
- Philoctetes on Installation Instructions
- star trek gold on Intercepting the request and/or response before and after processing
- shan on Parsing a result object from SOAP::Lite
- Benjamin on Installation Instructions
- Tim Collins on Installation Instructions
- loki on Support
- loki on Support
- loki on Installation Instructions
- Robert Ngo on Support
Recent Posts
- SOAP-Lite 0.70_xx pre-releases
- "SOAP::Sanity" - a guide for building complex data types
- State of the SOAP
- Announcing SOAP::Lite 0.67
- Documentation gets a face lift!
- Bowing to pressure, Byrne releases SOAP::Lite 0.66
- Support for HTTP 1.1's Expect: 100-Continue
- SOAP::Lite 0.65 Beta 6 released!
- 0.65_5 Released - Critical update for XMLRPC users
but is it true for the SOAP server programs also, if we want to return the information to the client in the xml format with just the tags that we want to be specified?
Posted by: | February 08, 2005 at 08:45 AM