Hi folks!! I have a big question and I'll appreciate some comments. Suppose I have a RPC style webservice with a complextype. Can every kind of clients (independent written language) acess a webservice like this one or just Java clients? What is the best way to provide this webservice? RPC or document? Thanks Pablo
Sounds like the best way for interoperability is document. That's why WS-I rallying cry is "rpc/encoded is dead; long live document/literal!"
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community
Joined: May 19, 2003
Thanks Jean-Louis! I have seen a lot of papers and I'm convinced document/literal is the best choice. But my problem is that first I write my session bean and deploy it. When I try to get the wsdl file using ?WSDL I always have a rpc/encoded on JBoss. What is the way to provide a document/literal webservice using Jboss/Axis? Thanks Pablo Belo Horizonte - Brazil
Joined: Nov 12, 2001
No idea about jBoss and the way it uses Axis. What I have seen so far is that all SOAP tools use RPC/Encoded by default. I do not know if and how you can change that with jBoss (but I would be surpised if you can't) Most of the time, there is special flags to use during generation, to specify you want to use Document/Literal or RPC/Encoded. For instance, with Axis Java2WSDL, you've got : -y, --style The style of binding in the WSDL, either DOCUMENT, RPC, or WRAPPED. -u, --use The use of items in the binding, either LITERAL or ENCODED