Interoperability 101 I found I had made my task of providing web services to legacy VB6 and .NET 2003 applictions more difficult than it needed to be. I started with the published docs and Wiki articles that emphasize documentliteral as the best way to achieve interoperability nirvana. While this may comply with WSI standards a more relevent question is "how do your existing legacy apps want to talk"?
The PocketSOAP toolkit I use to auto-gen VB6 proxies (as well as MSSoap toolkit) works great with wscompile's default of rpcencoded. .NET 2003 and new .NET 2005 work great with rpcencoded as well. Now I am in 'happy land' deploying in JBOSSWS over JBOSS 4.0.2 and I have less non-value added code to deal with. My client proxies are not stuck using send and response wrappers nor do I need to write beans to wrapper my arrays of complex types that are returned from many of my methods (I have no web service methods that use arrays of complex types as parameters). Are there limitations to rpcencoded that lead to WSI's backing of documentliteral? Certainly. Does rpcencoded work for everything I need in my existing use cases? Yes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3902641#3902641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3902641 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
