Hi, After lurking on this list for the last month or so as well as reading various articles, I convinced myself that I had better start using doc/literal encoding for the rpc style web service that I am working on - even though things were working pretty well using soap-encoding (using php and soap::lite on the client-side and java on the server-side).
Not suprisingly, after switching to doc/literal encoding, I started getting different, not so desirable, results. Specifically, the java Maps I was passing from java to perl were no longer being deserialized as real perl hashes on the the perl-side. I still haven't figured out what I am doing wrong but before I torture myself anymore, I need somebody to tell me why I shouldn't just go back to using soap-encoding. I understand soap-encoding is vague in certain respects and makes life more difficult for the toolkit implementors but what about us folks who are just building apps? Why should we care? I know my WS works with soap::lite and I am pretty sure it will work with dotnet. Lacking any real world experience in using WS I am struggling with these questions. For what its worth, I noticed that both the amazon and google WS apis use soap-encoding - should I be taking any solace in that? Thanks, Paul
