The mysterious element you're seeing is because you're returning an anonymous element of some sort. You can get around this by either writing a custom serializer or returning SOAP::Data objects. There was an article on Majordojo about this. (I highly suggest reading all of the SOAP::Lite articles on there, if you're going to be spending much time with the module. (note -- SOAP::Serializer as distributed in CPAN is different from the SOAP::Serializer package within in SOAP::Lite; look at SOAP::Lite for SOAP::Data, as well)
Also, based on the format you described, you're looking more for wrapped document/literal as opposed to SOAP::Lite's default, which is RPC/encoded. (here's an article that explains the differences). There's going to be options in SOAP::Lite to supress the automatic namespaces, but I don't know if there's a way to supress the type attribute built in yet. (I haven't been keeping up with the latest betas, I just went to look at the new site design that was mentioned today on the mailing list) You can always override the serializer to do it, though.
In reply to Re: .net-friendly soap messages with Apache::SOAP
by jhourcle
in thread .net-friendly soap messages with Apache::SOAP
by theblop
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |