Lists Home |
Date Index |
Joshua Allen wrote:
> Actually, it *is* possible to take a standard WSDL and hook up async
> bindings in BEA and VS.NET and have it "just work".
Do you happen to have an example that I could pump through "wsdl.exe"?
> ... Of course, you need
> a competent admin to bridge the JMS and MSMQ, but otherwise it will
> work. The part where things fall down is when you try to hook up
> bindings that tell what the expected response/request patterns are.
> This is because the Microsoft and BEA ways of representing in WSDL rely
> on non-standard extensions, and the standards haven't caught up. So
> orchestrating between these different systems requires a lot of manual
> work on both ends.
I'm hearing quite a bit about what WSDL does and doesn't do but am
confused about what SOAP is doing here.
Is it generally the case that the types are declared in XML Schema and
that a tool like "wsdl.exe" is used to generate bindings? If so, then
presumably "section 5" is not being used. And of course the HTTP/RPC
bindings are not used.
Is the SOAP Header used? If so, with what kinds of values? May faults be
and results be returned? May I mix in Internet protocols such as SMTP or
HTTP between BEA and VS.NET?
What would I lose if I sent pure XML and used wsdl.exe to generate
bindings from an XML Schema?