Here is the story.
rpc/encoding was invented first when xml schema was not finalized yet. So it
worked great then. But it led to hell lot of interoperability problems, that
the industry as a whole had to work towards WS-I, which felt that xml schema
was rich enough for literal encoding.
rpc/
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 t
.Net does "parameters" in both the input/output message parts for doc/lit
wrapped, whereas wscompile does parameters/result in input/output message parts
- just to be in line with how rpc/style web services is done.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic
Jason,
No criticisim intended when I noted a limited response. I certainly did not
expect someone from JBOSS to explain pros/cons to me. I simply took the limited
response as an indicator that not many folks had been down this particular
path, or if they had they did not have any particular ins
I don't see how we didn't respond. Your last post didn't look like a question.
We added automatic request/response object unwrapping for document/literal to
4.0.3 which was recently released.
-Jason
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3901857#39018
After getting a virtual non-response to my original post I have decided to go
back to the web services development environment I have used in the past
(Axis). After giving JBOSSWS a shot and dealing with increased interoperability
hassles and more required 'plumbing' code (like beans for arrays
Yes, by clunky I was referring to the need to use the request and response
types for my .NET and legacy VB6 client proxies. I like the cleaner interface
that simply mimics the Java interface used to define the service.
With that in mind I am planning on proceeding with rpcliteral as the default
By clunky are you refering to the fact that .NET wraps everything with an
object?
Their is a trick to get around this, and that is to edit the wsdl file and
change the message name of the return and input messages to be "parameters".
This is how .NET decides to unwrap messages.
I believe that
